Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Klenkes

  1. FF 58? That's interesting! The "girls" said that the problem started about 10-14 days ago. Perhap the problem was introduced to FF with V 59? Doesn't matter. It also happens on CKE's own demo. https://ckeditor.com/ckeditor-4/
  2. I know. But the content editors are women in their end thirties and who am I to argue with them? I don't have a death wish I filed a bug report with CKE and it was closed with a note that it is FF issue. https://bugzilla.mozilla.org/show_bug.cgi?id=1452906
  3. Thanks. I didn't find anything either. I will file a new one. There are a few ways to avoid the error but for now I recommended to use Chrome instead of FF. These are professional texters and they are used to work in a certain way(we all know the feeling). But they will have to adapt for now. Thanks for testing.
  4. Really? I tried with Firefox Quantum 59.0.2 32Bit and 64Bit on https://ckeditor.com/ckeditor-4/ and can reproduce it... But what does it mean? I will read through the issues first.
  5. This morning a client contacted me with a strange problem. At first I couldn't reproduce it because I use Chrome but then I realized that it only affects Firefox and CKE fields. If you type some text and then press SHIFT+ENTER to insert a <br> then wirte some text in the second line and then place the cursor at the start of the second line and hit backspace, the cursor jumps to the wrong position. The clients content editors are extremely frustrated by this because they have to search for the cursor I can reproduce this behavior in almost all PW versions, even a clean install witout any CKE plugins. This whole behavior seems somehow familiar, like I have heard it before, but I can't remenber... Anyone knows a solution except using Chrome?
  6. Long thread made short: On most of the websites I maintain I had to put this in init.php: setlocale(LC_ALL, "de_DE");
  7. Field level access only protects the field from being shown on the frontend. The file is still accessable through an URL.
  8. You are the man! Tomaten auf den Augen! Is there an english expression for it?
  9. Emailaddresses in CC array keep being encoded I have a small module with a function that sends emails to me(Admin) and users who act as moderators. What I want to do is basically this:(from first post here) $options = array( 'sendSingle' => true, 'cc' => array('person1@example.com', 'person2@example.com', 'person3@example.com') ); $numSent = wireMail($to, '', $subject, $textBody, $options); But I want to CC to users of a certain role, and retrieve the users like that: $address_rev = wire('users')->find("roles=revisor"); Now I have to build the array for the $options: foreach($address_rev as $one){ $emailcc .= "'" . $one->email . "',"; } $emailcc = rtrim($emailcc, ',');// remove the last comma $options = array( 'sendSingle' => true, 'cc' => array("$emailcc") ); But sending fails with the quotes being encoded by PWs sanitizer(I assume) Invalid email address (&#039;person1@example.com&#039;, &#039;person2@example.com&#039;) (in path_to....\wire\core\WireMail.php line 105) Why? It doesn't happen when I hardcode the array like in the example, and when I echo my array it looks just fine. How do I build the array to populate the cc array? Or what am I doing wrong? PW 3.0.84 WireMailSMTP 0.2.3
  10. Who would have thought... a pirate to the rescue! A quick, configurable and functional solution to my problem. HARRRH to you!
  11. If you set the correct family settings to the parent and child template, then the children can only be placed as a child of template for pageA, pageB, pageC, ... but as I read your post again... I guess you don't want them to change parents as well?
  12. It would have to be something like: $pages->find("has_parent=$page->parent, template=subitem-template, switched=1");
  13. You could try another approach but it depends on how you manage shopowners in the backend. If they can register themselves it will be a little more problematic, but if an admin creates shopowners you could try: Create a page /shopowners/ (with its own template) and create pages as children for each shopowner with a title field(default) and a page reference field which points to the users page. On the page /shopowners/ you then don't query the users, but the pages unter /shopowners/ with the page reference ID. With this ID you then get the content and your url would be /shopowners/shop-owner-name/ Same goes for /shopowners/shop-owner-name/ Get the page field ID and retrieve the content for the user. Another approach would be: Just like the above with the page reference field But keep the user page data to a minimum just with username, language and password Store all the public viewable data in the pages under/shopowners/shop-owner-name/
  14. Crysis for 5 bucks and Grim Fandango for free! A nobrainer. There goes the workload of today...
  15. Looks like it handled required fields right from the start.
  16. Thanks for the pointers. I cleaned up the variables and added default values for the button. Also got rid of the generation of the second button. Is a copy anyway. I agree. This would be cool but perhaps beyond my skills as I patched stuff together from AutoSave. I will look into it...
  17. Well... there it is: https://github.com/Klenkes/AjaxSave At the moment the only configurable setting is the button text. I tested with all kinds of configurations and found no problems except admin theme UiKit shows the message box twice for a second. I'm sure the module could use a "cleaning" hand from a Pro
  18. 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.
  19. 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.
  20. 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.
  21. 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
  22. 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.
  23. 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.
  24. 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>';
  25. or echo $pages->get(1234)->siteChairperson;// where 1234 is the id of the settings page
  • Create New...