Jump to content

poljpocket

Members
 View Profile  See their activity

  • Posts

    166

  • Joined

  • Last visited

  • Days Won

    6

poljpocket last won the day on December 11 2024

poljpocket had the most liked content!

1 Follower

Profile Information

  • Location
    Switzerland

Recent Profile Visitors

4,877 profile views

poljpocket's Achievements

Sr. Member

Sr. Member (5/6)

198

Reputation

  1. poljpocket started following Remove child links from a parent page , Digital Ocean Load Balanced Setup with ProCache , 404 page not found when debug mode "True" and whith textarea field and 3 others
  2. poljpocket
    Another approach is to use NFS to share a volume across Droplets. NFS tutorial from DigitalOcean themselves: https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nfs-mount-on-ubuntu-20-04 Here is a source which uses Docker but the concept is the same: https://www.infraspec.dev/blog/nfs-fs-as-docker-volume/
  3. poljpocket
    Hi Dave, Thanks for clarifying. In ProcessWire, every page has a parent (the only exception is the homepage which always has ID=1). So the best you can do is set the homepage as the items' parent to factually "clear" the parent. Observe that the permalink thus will be /{$page->name}, which factually means, they don't have a parent. To keep things organized though, I think you already did what you are supposed to do: create a new parent page and move all the race pages there as children.
  4. poljpocket
    Hi Alexis, I think if you upgrade from a version so old, there will be problems. First of all, yes the new master version is just around the corner but 243 isn't the stable release just yet. For now, try using the master version, a.k.a. 229. Next, I think your 404 errors might stem from a routing problem. Try comparing the .htaccess files in your root directory. Since this is outside the wire directory, it might not be the newest version and in that many years, there might have been changes. If that doesn't help, have a look at the logs directory (site/assets/logs), specifically for exceptions and errors. They might lead you to what the problem is. Feel free to post any errors here which might help us to find the problem together.
  5. poljpocket
    Are you maybe missing the .htaccess file in your root directory? If you're copying files around with Finder, it won't move the .htaccess files which aren't in a subfolder.
  6. poljpocket
    Happy new year to you too! Could it be that you are dealing with mixed content problems? Can you try using http://localhost instead of https://localhost (note the s)? Did you set the httpHosts property in config.php to be localhost?
  7. poljpocket
    This will be fixed in the new master version :) https://github.com/processwire/processwire/commit/29b1fa0e4583db77babf699a6ea3bb062903060f
  8. poljpocket
    This could also be a browser issue. One example would be a cached 301 redirect from an old staging install on the same URL. Modern browsers are caching these forever and it's a pain to make them forget the redirects.
  9. poljpocket
    Hi Dave, can you elaborate a bit on what your goal is? I assume, you have the links to the child pages somewhere on the website (the part your visitors see), right? What do you mean by "unlink them"?
  10. poljpocket
    Yep, see the first two screenshots in my post above 😁
  11. poljpocket
    And even more. This is how the page names and titles show up in the database. Looks like it is using some non-standard punycode to encode the names and this is also where everything seems to break:
  12. poljpocket
    Some more peculiarities which might help us:
  13. poljpocket
    There you go running on the same test install from above: You are on to something here.. that looks very inconsistent! Note how the page name in the log message is always correct but shows wrong in the "Settings" tab.
  14. poljpocket
    You are right, copy-pasta mistake. I just copied your stuff over. But I corrected it right now and it doesn't make a difference (and yes, it's only about the rewrite rules and doesn't affect the PW admin in any way). Maybe you will find something with the hooks I have talked about above.
  15. poljpocket
    You can maybe start by looking into where the problem occurs. You can for example use Tracy's bd() function to output the page name before and after every saveReady and saved hook. This will at least let you see in which part of the code you have to go dig for more. Do you have any hooks already in use for Page::saveReady and Page::saved? On which PW version are you?
  16. poljpocket
    You are obviously right! I am sorry... I tried your settings in a quick-and-dirty local Docker install using the blank site profile. I can use your whitelist no problem: This is what I added to the files:
×
×
  • Create New...