Jump to content

horst

PW-Moderators
  • Posts

    4,049
  • Joined

  • Last visited

  • Days Won

    86

Everything posted by horst

  1. Oh sorry to be not clear. I will update my initial post later with a link, when I'm back in the office. I'm speaking about the SEO yoast plugin for w*rdpr*ss, and available for other CMSs and as a bare JS libeary too, if I had read it right.
  2. That's a good Blog post! I really want to read a part two, (and maybe three?). πŸ™‚ Also very useful for new starters, I believe.
  3. Hey @Pete, I do not see any possible improvements with your code. (So this also may be a bit because my CLI knowledge of this tools maybe a bit lower as you expect. 😁 - On my local machine I (can & do) use other tools for those things. πŸ™‚)
  4. @bubu2110 have you already had time for a look into your Inbox? πŸ˜„
  5. @dotnetic Jens, when do we get an update to the latest stable? 3.0.200 πŸ˜‰ Or is it already online and I haven't found it?
  6. when it says 2) install the PagePaths module, you can find the module under modules > core in the admin. By default, the search through urls and paths is disabled, but you can enable it by installing given module.
  7. Ah yes, there it is still in plain text too, but also the DB credentials are. But looks like a better solution indeed. Best practise is to have one single config.php file only, that one on the live server. No copies in GIT. And not a plain password in every DB dump! Thanks @fliwire
  8. I'm not sure I understand completely. The password is saved in the DB (module config). If this can be read by someone, you have much more problems then a single smtp password. πŸ™‚ The smtp sending process explicitly needs the password passed in as plain text. So, if we would encrypt it before storing in DB, we would need to decrypt it before sending. If we use hash or salt, or keys etc, they must be stored somewhere (DB?). So, this would not be a "better" solution. Any ideas by you?
  9. Short thoughts (on mobile ATM): PW cache API, PW template cache, PW ProCache, PHP memcache(?) AFAIK, Apache without ProCache handover a request to PHP, PHP has everything to rebuild what is not cached in some sort (cache API for pages or chunks of any sort; template cache for a complete template markup, or a complete "php page" in memcache). When things have to be rebuild, the mysql server gets involved too. At best would be PC, omits PHP and MYSQL; second would be PHP, it omits the MYSQL server; somewhere in between is a mix of cached and uncached bits that builds a complete page markup. Another strategy, (if its practical depends on your project(s)): serve a more or less bare HTML markup, with maybe direct content only for header section, H1 and first paragraph(s), and fetch all under the fold with progressive lazyloading (wide threshold). Or a combination of all. πŸ™‚ EDIT: additional: If you need to serve individual pages for each request, check your fields setups. Maybe you can "move" or optimize some parts to get be prepared on page save in the admin. (additional fields, hidden for the editors, that can contain combined data, that lowers the number of db requests for visitors, at a small cost for the authors on page save)
  10. I never had the need to use raw text searching upon JSON objects. Looks a bit fragile to me. Have you thought about alternative storing strategies, other field types?
  11. Hi Robin, I think one can do that a bit simpler, at least I always use it this way: 1) I'm not hundred percent sure, but maybe there is difference between cloning the whole template compared against only duplicate the fields. (Cloning definitely includes all settings under family, files, advanced, etc) 2) And this saves the creation of an extra template file. All in all very useful when I want to use something like a single controller file, that calls different view files upon the template names. πŸ™‚
  12. Whats about using public state for those that can get listed in menus etc, and hidden state for the others?
  13. Hi, good news: Ryan has fixed this with a commit today. So if you are able, you should switch to the dev version from today. (And do no longer use my workaround! It adds to much overhead.) https://github.com/processwire/processwire-issues/issues/1497#issuecomment-1106543260 https://github.com/processwire/processwire/commit/6fcd7a70389450631932aa0fd4a0a703d3ac8804
  14. I think this is wrong. The root is exactly the directory where the PW index.php is stored: https://processwire.com/api/ref/paths/
  15. Maybe something like this can work? if(!$this->wire->input->get->id) return; $editedPage = $this->wire->pages->get('id=' . $this->wire->input->get->id); But, if it is to early in the process, the page doesn't have an ID, So I'm not positive if it is right to hook into processing the initial form, or if it would be better to hook into before displaying the editpage with the error message labels? (And do another redirect after correcting the missing values).
  16. You may try to use the page saveReady hook in ready.php to do a check and conditionally correction. But this would also be called / applied when everything is ok. Or, if you want to have a more optimized solution, you can check the possible involved methods : A search in the wire folder shows me this above result, where I would first check the ProcessPageEdit module, but don't know really.
  17. How is the error? Which error message? Do you get a error stack with turned debug on?
  18. I think this is available since forever. Check all config paths properties, especially: $config->paths->root
  19. Hi guys! ( @howdytom @olafgleba ) Please are you able to post your setups / configs to this github-issue? I think this would be of great help for Ryan. Please put in your image sizer config settings, the lines of code how you use and where you use it. (template-file, repeater, etc) Also please only issues with the core image field. I had posted example code there, to help reproduce the issue in an automated way, but I think that Ryan now think that the issue only is with my special code. !! Many thanks!
  20. Ah, - what about a DB dump without inserts for caches? Have you one and can upload it through phpmyadmin or the like? (Thats instead of module refreshes, without needing the admin IF) Otherwise you have to switch back to wire 3.0.148 first.
  21. I always do wire version switches including this steps: with old wire version, make a db dump, but for all caches use drop table, create table, without inserts. Or, if you are able, remove the inserts in the live db. remove all files within the cache disc subdirectories switch wire folder, load the admin for 2 or 3 times Then its done for me in 99%.
  22. the author of that article, Daniel Berger, once in 2015 or 2016 has written a good article about PW in c't. It was over 4 or 5 pages and was very detailed. https://www.heise.de/ct/entdecken/?jahr=2016;ausgabe=25;sort=seite_auf;seite=6 https://www.heise.de/ct/ausgabe/2015-7-Websites-betreiben-mit-dem-Open-Source-CMS-ProcessWire-2562549.html
  23. @bernhard Are you talking about apache server timeouts for php script requests? If so, you must be able to set_time_limit(##) as recuring call, maybe whenever the keep-alive-ping also is sent. (every 15 seconds for me)
Γ—
Γ—
  • Create New...