Jump to content

Klenkes

Members
  • Posts

    402
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Klenkes

  1. Turns out it wasn't that hard after all! I "reworked" Somas AutoSave to my needs and, to my own surprise, it works fine. Have to test it though on more complex page structures and fieldtypes. After three years "living" with PW I am still amazed how easy some things are. Even for me.
  2. Budget is not the problem, I love Ryans ProModules! But I never had the need for ProDrafts with all its fancy features and just for an apply button? But it would be worth it. Just to peek into it and see how it is done.
  3. Ah thanks. I will take a look at it! Autosave may not be an option but maybe it can be adapted to use an ordinary button.
  4. I know. But unfortunately it's just an ordinary save action and the page is reloaded with scroll to the top of the page and all fields closed again
  5. The more I work on projects that have lots of fields, lets say on a produkt page, I miss an "Apply" button that saves silently in the background without reloading the page. Imagine your fields are organized in fieldsets, and for a good overview they are set collapsed. Each time you save your page you start new by scrolling down, look for your fieldset, open your fieldset, look for your field, and place the cursor again where you left off. Example: Unless there already is a feature like that and I missed it this is my feature request.
  6. I absolutely understand the position you are in. In my 20 years I saw a lot of CMS, switched because they took a wrong turn in development, or were overcomplicated. With PW I finally feel at home. Let me give you some advice in the steps you should take: Install PW locally with the intermediate profile Look at the templates, especially _main.php, _func.php and what's going on in there Then take a look at Selectors. Read for a while and play with them in your template Create new fields, add them to templates and use your new knowledge with selectors! Look at imagefields, text and textarea It won't take long untill your first Aha-experience! Play with the structure of your pages and adapt your selectors(select parents, parent->parent and children) Bookmark the Cheatsheet and look at it often It won't take long - believe me. And a whole new world of possibilities will open up to you! I have been there.
  7. MarkupSimpleNavigation is really nice if you show the real path of your document structure in your url. But in your case you always show the parents url, then I would go another way and do it yourself like: echo '<ul>'; foreach($pages->get('/')->children as $item){ $class = '';// for marking the parent li if($item->id == $page->id) { $class = "parent"; } echo "<li class='{$class}'><a href='{$item->url}'>{$item->title}</a>";// open toplevel li // if there are childpages if($item->children){ echo '<ul>'; foreach($item->children as $anchor){ // you would have to set the anchor targets to the name of the page // note: $item->url # $anchor->url because you need the parents url echo "<li><a href='{$item->url}#{$anchor->name}'>{$anchor->title}</a></li>"; } echo '</ul>'; } echo '</li>';// close toplevel link li } echo '</ul>';
  8. or echo $pages->get(1234)->siteChairperson;// where 1234 is the id of the settings page
  9. Same on iPad in landscape, but NOT in portrait orientation!
  10. When trying to modifiy a field of type Multiplier(V13) I get an error: Error: Call to a member function get() on null (line 317 of D:\Projekte\kopfleere\processwire-dev\www\wire\modules\AdminTheme\AdminThemeUikit\AdminThemeUikit.module) Line 317 states: $fieldset->collapsed = !$field->get('themeColor') && !$field->get('themeBorder') && !$field->get('themeOffset');
  11. Thanks al lot!!! This is the first howto I actually understood! The only thing I noticed is, that if I change the name of a page in the default language(now not EN anymore), all other name fields are changed to the same value as well. Strange...
  12. I think not. The error occurs for me on pages with no repeater on it. Or perhaps I misunderstood...
  13. I second that. I cannot insert a link or edit a link in CKE on templates with FieldsetPage.
  14. Rewrite Base isn't active by default in PW htaccess. # RewriteBase / While my hoster is fine with it, on some servers I have to enable it to make rewrite work.
  15. Mhh... I think I ran into this problem before and solved it somehow, but can't remember how... 'item_tpl' => '<a href="{url}">{title} <span>({numChildren})</span></a>', The {numChildren} counts hidden and unpublished item as well.
  16. Just in case someone else encounters the same problem: I had to migrate a whole website to PW and during tests I imported around 200 pages. Now I wanted to delete them and start the real import process. To get rid of the test pages I tried to delete them with adrians AdminActions, but got an error message and nothing was deleted: Error: Call to a member function path() on a non-object (line 261 of /xxx/site/assets/cache/FileCompiler/site/modules/Pages2Pdf/Pages2Pdf.module) I had to detach the template in question in Pages2Pdf settings. Then it worked and I was able to delete the pages. Same error with a ListerPro Action(Delete), so I asume it's a problem with Pages2Pdf... PW 3.0.62 Pages2Pdf 1.1.7
  17. Just to let you know: I did a few more tests with and without "Use ACF" and it seems to work just fine! All happened on PW 3.0.62
  18. #2 makes sense. A quick test shows no problems and it seems that the fields settings are respected. I will do further tests the next days.
  19. That explains a lot For the sites I migrate to PW option 1 would me my choice, because importing the content is the first priority and editing the content comes later. Nobody wants to sift through a few hundred pages to make it all like it was. In my case editors are skilled, trusted and would be fired if they do monkeybusiness with the HTML. ...but then again... option 2 would work as well since I already deactivated all the purifier options for the fields anyway. For now I will go with the dirty fix
  20. Me again... I imported a few hundred pages to more than 30 parents and almost everthing is fine. Then I noticed that all custom ids and classes in my imported textareas were filtered out during save, even with deactivated ACF and HTML Purifier(in textareas settings) Pasting in the same HTML in source mode afterwards leaves the custum stuff alone. So it works. I don't even know wether it's a BCE issue or with Profields textareas? This problem seems familiar but I can't remember...
  21. I thought about mediumtext but don't know what "unwanted" effect it may have on other PW functions. I went the even more simple way and import now to a single import page, and then move the imported pages with your great AdminActions to their destination parents. This way I don't have to configure all parent pages with my fieldpairings. BTW... thank you very much for AdminActions. Without Move and Search and Replace this project wouldn't be possible.
  22. .With adrians great Admin Action module
  23. Just ran into a funny problem. Well... not really funny, but it took me way too long to figure it out. (Sometimes I wonder how get through the day...) I am developing the migration of 10+ similar sites from another CMS to PW. All the websites have lots of fields and data, and BCE is the only way to map the data to textareas subfileds. All tests worked great so far until now! Suddenly I was unable to input my fieldpairings. ProcessWire: ProcessPageEdit: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'data' at row 1 As I said it took me way too long to realize the "Data too long for column data" During my testing the database field 'data' got filled up with all the settings for all the parent pages, and since it is of type text, I guess 64kb is the limit. I had to uninstall and reinstall BCE to start over with an empty data field. I guess there is no real solution to this but I wanted to add it here in case somebody faces the same dilemma.
  24. I think the problem is that in the moment of adding the new page the ID ist not known yet. So, the logical steps would be: add the page and then rename it. The issue has been discussed before.
×
×
  • Create New...