Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

73 Excellent

About celfred

  • Rank
    Sr. Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

4,871 profile views
  1. Hello, I am still using this module a lot on my site but I would like to avoid the reloadign of the page. Is this possible ? Let me explain : I use edit links as follow : foreach($concernedPages as $p) { echo $p->title.' '.$p->feel(array("text"=>"[Edit]", "fields"=>title,image,summary,level")); } So as you may imagine, I have a list of pages titles accompanied by an 'Edit' link. When I click this edit link, a lightbox opens up and I can edit the page.and this works fine BUT, when I hit the 'save' button, my lightbox closes and I wish the current page (which is not the page I have just fronend edited) would NOT reload as well. Would there be a way to test if the current page is the edited one and reload if true, but prevent reloading if false ? Or simpler, just manually set reloading to false when we want it, resulting in the following code : echo $page->feel(); // THIS WOULD RELOAD CURRENT PAGE AFTER EDITING foreach($concernedPages as $p) { echo $p->title.' '.$p->feel(array("text"=>"[Edit]", "fields"=>title,image,summary,level"), 'reload'=>false); // THIS WOULD PREVENT RELOADING (NOTE THE EXTRA PARAMETER ADDED TO ILLUSTRATE MY POINT } Thanks for helping ! PS : I hesitated on creating a new post but eventually decided on following this thread (I have read the complete thread but couldn't finc anything concerning my question) EDIT : Eventually, I guess I've found it myself (and it wasn't so hard) adding this in my main JS file : var FEEL = { onBeforeReload: function (o) { return false; } };
  2. As a follow-up, @ryan had a look at this and made a patch that somehow tests the Mysql version and does something that makes it work fine (at least on my localhost). Technically speaking, I am unable to explain all this, so I prefer let the pros give details if needed, but just know the issue seems solved. As I said on Github, I am quite glad I have been able to somehow contribute to the community. You all have provided me with so much help since I have discovered PW. THANKS again !
  3. @kongondo Great idea ! I've just tested and it works with other fields : title, summary... No problems (apparently). As soon as I change to "name~=", the error triggers. I'll go ahead and write this as well on the 'bug' report.
  4. @kongondo I'm just noticing that my previous message didn't go through... I was saying that for your information, I had replaced all my ~= operators with either ^=, ~*= or = depending on my use cases. It did the trick although I'm losing the original 'whole words' searching capability... but at least I'm not stuck πŸ˜‰ I wen tahead and submitted a 'bug' issue as you advised. Not sure this is a real bug since I have a feeling somebody else would reproduce it if it was, but I di dmy best explaining the issue and I hope it can help ! If anybody needs more information about it, just ask. I'll keep an eye on this issue since I would like to understand and solve it in a better way ! But thanks again for your help !
  5. @kongondo Thanks for your reply. Ah... And downgrading MySql doesn't seem possible (at least for my low skills... - https://dev.mysql.com/doc/refman/8.0/en/downgrading.html So I guess I'm gonna be in trouble here...
  6. @kongondo Thanks for your reply. Ah... And downgrading MySql doesn't seem possible (at least for my low skills... - https://dev.mysql.com/doc/refman/8.0/en/downgrading.html So I guess I'm gonna be in trouble here...
  7. So nobody has any clue for me 😞 ? On my localhost, I have : PHP version is 7.4.3. MySQL version is 8.0.21. Maybe this can help... I have a feeling if it was just a configuration problem, all requests should end up with the 'illegal argument to a regular expression' error ? But I can't imagine PW would be the cause (otherwise I vould get some clue from the community, I'm sure πŸ˜‰)
  8. Maybe this can help. The error points to this file/line. File: .../wire/core/WireDatabasePDOStatement.php:166
  9. Hello, I've just upgraded to 3.0.165 (and updated my Ubuntu version as well) and on my localhost, I am facing a weird issue : all my requests having the ~= selector cause a Mysql error with this message : PDOException #HY000 SQLSTATE[HY000]: General error: 3685 Illegal argument to a regular expression. I have no idea what is going on. If I change my request from $visualizer = $pages->get("name~=visualizer"); // Triggers the error to $visualizer = $pages->get("name=visualizer"); or $visualizer = $pages->get("name~*=visualizer"); My code works fine again. Any idea ? Shall I change all my requests (but from what I understand by reading the documentation, ~= exists and fits my needs : all words in any order [though I do understand that in my example above it may be useless since I have only one word]) Thanks !
  10. Hello, Just a mention that today I have received this newsletter from The Whale : https://thewhale.cc/91 And Processwire is part of it πŸ™‚
  11. That's what I keep telling myself but I often end up having a greater and more difficult challenge πŸ™‚ On my side, front-end editing seemed a good solution because I may have up to 50 textareas to edit and if I have to click on each in back-end, save and go to another, having a rather slow connection, can be troublesome... Here, I can load all the 'alerted' textareas on 1 page and edit them 'right away'. It was then just (!) a matter of automatically detecting who was the last user to modify the text. But nevermind for now, as you said, I still have learned a lot trying to do that ! Thanks a lot for your encouraging message and your help !
  12. Thanks @bernhard for your reply. This helps me feeling more confident about my tests since I often don't know if I'm going in the right direction. I must admit I am not mastering anything there (you can tell !). I was glad to learn about the 'Event interceptor' but it seems like it lead me on a false interpretation πŸ˜‰ So hooks don't fire when front-end editing ? I don't really understand why since the field is actually saved, isn't it ? So I guess I won't be able to avoid my 'Manually check this box to alert your teacher' way of doing πŸ™‚
  13. Still desperately trying things... I have this in my ready.php : $this->addHookBefore('Fieldtype::savePageField', function (HookEvent $event) { bd('ok'); // Also tried fl(), d()... }); I have nothing anywhere (after front-editing my textarea and clicking 'save' in my CKEditor) aven after reloading the page, whereas if I use the event interceptor, I get the whole list of fields being saved (after reloading the page) and I can see that one of them is the field I have just edited. So I'm stuck 😞
  14. Thanks a lot @Zeka for your reply. I do use TracyDebugger in my usual debugging 'flow', but my problem here is that it never triggers anything, and that is exactly what I don't understand. After trying some more things, I can understand thath Tracy works in hooks by testing this : $this->addHookBefore('Page::render', function(HookEvent $event) { bd('ok'); }); which does give me a result on page load. Eventually, my concern is there : in my initial question, I want to debug in a hook that doesn't completely reload my page. I guess that's why I can't see anything. When I double-click my textarea to front-end edit it and then hit 'Save', the page doesn't reload so my dump bar stays silent. Is there a way to dynamically see what's going on ?
  15. Still digging... I have tried this taken from the docs : $wire->addHookAfter('Pages::saved', function(HookEvent $event) { $page = $event->arguments(0); $event->message("You saved page $page->path"); }); But I see nothing... My logs > messages do not show anything, my Tracy bar doesn't show anything... Does a front-end edition and a hit on the 'Save' button does not trigger the hook ? I have a feeling I was confusing things in my previous post, so all in all, let's sum up my question : how do you debug hooks ? Is a simple bd('ok') suppose to work if the hook is working ?
  • Create New...