Jump to content

Spiria

Members
  • Posts

    65
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Spiria

  1. If you want to use classes, you must also include this $config->usePageClasses = true;
  2. Be sure to have this in your config.php $config->useFunctionsAPI = true;
  3. Hi, Here is a short tutorial on my vision of routing in ProcessWire. https://www.spiria.com/en/blog/web-development/tutorial-routing-in-processwire/
  4. Here is another little tutorial about files structure in ProcessWire. https://www.spiria.com/en/blog/web-development/tutorial-the-file-structure-in-a-processwire-site/ Comments welcome as always.
  5. A little I wrote about template rendering in ProcessWire. https://www.spiria.com/en/blog/web-development/tutorial-processwire-style-rendering-strategy/ Comments are welcome.
  6. In fact, switching the diacritic corrections to off in French resolved the problem. "ne" is set to be corrected into "né" when you are in English.
  7. I have however another stranger and more important problem in French. Every "ne" which is the negation in French, is replaced by "né"!!!
  8. I have a strange problem which is also present with another fork of php-typography. All the letters are spaced... I had hope that your module would have not the same problem. It seems related to the locale. Putting set_space_collapse to false resolves the issue. https://github.com/mundschenk-at/php-typography/issues/137
  9. Thanks. It was too early in the morning 😉
  10. Is it set by default or should we set something somewhere?
  11. I have found the culprit. My developer put a hook in the ready.php like this: if (wire("page")->template->name === 'admin') { // Ensure Uniqueness of Emails across site $wire->addHookAfter("InputfieldEmail::processInput", function (HookEvent $event) { $field = $event->object; .... Commenting this whole hook removes the problem. Sorry to have bother you with that.
  12. I mean either disabling or uninstalling. Nothing happens except the "unrecognized path" error. So I tried to remove physically the module, deleting the cache folder, emptying the cache table in the DB (yes, BD is in French ;-)), emptying the session folder as well. Making sure there is no trace (no pun intended) in the modules table. Indeed, there is something strange about this installation...
  13. I will add a final thought. TD is the only module in this installation that I can't disable... I have to remove it by hand and clear the BD. Perhaps I am leaving something?
  14. Ok, thanks. So I am still in the dark. Tracy Debugger seems not the problem indeed. I have tried reducing the PHP version and reverted to the TD version suggested. Thanks for your kind help.
  15. Is this normal that not all the modules are displayed? Those disabled do not change a thing.
  16. Ah ah, I am not familiar of all the bells and whistles of your excellent module. Thanks again.
  17. I will try disabling modules, which is a PITA 😉 Thanks for the suggestions. I will let you know.
  18. I have indeed logged out and back. In fact, the problem is also on the production site which runs a lesser version of PW. I reinstalled also TracyDebugger and clean all the caches, but to no avail.
  19. I have a weird problem with Tracy Debugger. I don't know if it's related to the module, but I can't change the settings. I always get an "ProcessWire: Unrecognized path" error with a curious URL (/bookmarks). I don't have this problem with my other sites. They are all running under 3.0.171 at the moment, at least locally. Any idea?
  20. Hum, the site is 3.0.165. Thanks.
  21. Hello, I tried to install the SVG File Sanitizer/Validator module as recommended by ProcessWire (thus by @ryan 🙂 ). However, as soon as I enter "svg" in the list of allowed extensions, I get a nice red screen. I have to allow svg to bypass the validation. What is the problem?
  22. I am writing here instead of the ProCache forum because I have the impression that several nginx experts could solve this. In its new version, Procache proposes new .htaccess rules that are difficult to translate into nginx rules. We currently have a problem with the trailing slash of URLs which gives us a bad score in SEO analysis tools such as semrush.com. Indeed, a canonical URL is either without or with "/", but cannot be served by both options. Although ProcessWire without ProCache respects this rule, ProCache has no difficulty serving both, which is considered an SEO optimisation fault. I believe that ProCache version 2 solves this problem with these new rules, but I can't understand the following. Does anyone have any idea how to translate this into a nginx rule? Attached also the whole proposed .htaccess for ProcessWire. # PROCACHE v2/31885be14d6cfb4b2b0d3e533260bded -------------------------------------------------- RewriteCond %{REQUEST_METHOD} !=POST RewriteCond %{QUERY_STRING} !.*=.* RewriteRule ^.*/$ - [E=pwpcstep:pour,E=pwpcname:index] RewriteCond %{ENV:pwpcstep} "=pour" RewriteCond %{HTTP_COOKIE} !^.*(wire_challenge|wires_challenge).*$ RewriteRule ^.*/$ - [E=pwpcstep:stir,E=pwpcpath:%{DOCUMENT_ROOT}/site/assets/ProCache-00478359c5e65dbada1075bfbd4] RewriteCond %{ENV:pwpcstep} "=stir" RewriteCond %{ENV:pwpcpath}/$0/%{ENV:pwpcname}.html -f RewriteRule ^.*$ - [E=pwpcstep:drink,E=pwpcfile:$0/%{ENV:pwpcname}.html] RewriteCond %{ENV:pwpcstep} "=drink" RewriteRule ^(.*) %{ENV:pwpcpath}/%{ENV:pwpcfile} [L] <ifModule mod_headers.c> Header set X-PWPC "ProCache" env=pwpcstep Header set X-Powered-By "ProcessWire CMS, ProCache" env=pwpcstep </ifModule> RewriteCond %{REQUEST_URI} "^/~?[-_.a-zA-Z0-9/]*$" # /PROCACHE ------------------------------------------------------------------------------------- .htaccess-procache
  23. We have been asked for a project which will require that any DB transaction be made securely. My IT team has set a mySQL server in SSL for our tests. How is it set in ProcessWire? Are the config()->dbOptions enough to assure so? Has someone some advice, or code on that?
  24. My bad... everything is fine. A table name was not correctly written ...🥵
×
×
  • Create New...