Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Autofahrn last won the day on May 14

Autofahrn had the most liked content!

Community Reputation

382 Excellent

1 Follower

About Autofahrn

  • Rank
    Sr. Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

767 profile views
  1. Not sure if you refer to my experimental tweak to get a read-only demo view for the RepeaterFlex in admin: https://pwflex.team-tofahrn.de/?preview=PG132107923 There only was a miniature "discussion" in closed RepeaterMatrix section:
  2. A more complex approach would be a new fieldtype which allow to browse and select through the SmugMug API. Edit: just found this, which may help to go that way: http://phpsmug.com/
  3. Sure. Of course the backtrace only helps if you see a function get called (maybe unexpected or with bad parameters) and want know where this call originates from. This, for sure, is not a history log and not an alternative to the proposed hook log.
  4. At least it would tell you, from where your hook was called. For example, if its a pageSave hook, you'll see who is actually invoking $page->save. In this case you probably had seen, that the hook was invoked twice from the same originator. If that was a technical question, you'll either do this, to get a preformatted trace of the stack (not sure why I needed DEBUG_BACKTRACE_IGNORE_ARGS in my quick test): ob_start(); debug_print_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS); $preformattedCallStack = '<pre>' . ob_get_clean() . '</pre>'; Or dump the full trace data array using tracy: bd(debug_backtrace());
  5. Did you try debug_print_backtrace? https://www.php.net/manual/en/function.debug-print-backtrace.php Maybe there's a Tracy entrypoint to get this logged properly.
  6. You may try set_time_limit in your script: https://www.php.net/manual/en/function.set-time-limit.php
  7. maybe requested URL is wrong or does not handle the AJAX query in that case? ...only guessing, lack of knowledge about the inner workings... 😉
  8. No instant solution, but did you check in dev tools both request and returned data? If the JSON parser complains the response starts with a <, it seems to receive some HTML.
  9. $sanitizer->selectorValue("*"); effectively returns an empty string. So searching for nothing obviously isn't intended, but probably correct to return everything... 😉
  10. Finally fixed @arjen's issue, culprit was a non-readable file within the pwpc directory which wasn't excluded since I forgot exclusion paths need to be site relative (/site/assets/pwpc/ for all ProCache users).
  11. yes, instantly! Probably because name is handled something special. Maybe worth triggering @ryan...
  12. It's just manually enforcing the string is escaped in quotes, but single quotes this time. Since I guess that double quotes are removed somewhere, you may try with this one as well: ['title|name|indexer', '%=', '"'.$a_terms.'"' ] In both cases you really need to ensure the search term does not contain quotes itself, searching for "it's" will fail now. That's normally something $sanitizer->selectorValue() takes care of.
  13. Thanks for the pointer, searching for "&something" does not work with AjaxSearch either, since it sends the field unescaped through a get request, so "something" effectively gets a second parameter and the search string is empty (does not contain the ampersand). But that's another story. Could you try this line (or better run $a_terms through $sanitizer->selectorValue()): ['title|name|indexer', '%=', "'$a_terms'" ]
  14. Did you check for bad characters? Had this sometimes with copy&paste code from the forum. Modified the script a little to hopefully display a reasonable error message.
  • Create New...