prestoav

Hi @bernhard, This is super useful. Thank you and have a great weekend! Geoff.

Hi @bernhard and thanks for taking time to answer my question. I must confess, I had not considered the 'old pages' problem but what you say does makes sense. I'm not keep on the 'double negative' approach to the field instruction as, while it solves the technical issue, it doesn't feel like good UX for the admins, at least in my application. However, the idea of a hook to set that field on page creation does seem like a way forward. Thanks again.

Hi folks, Is there any way to setup a checkbox field so that is checked by default? I can't see that in the field admin and where. Thanks!

OK, solved it. For some reason the admin template was setup correctly. Templates > admin > access should be set like this: Mine was set to option C which meant, as a 'guest' before logging in, I had no permission to see the admin login page and was redirected to the main root of the site. Phew!

Actually, scrub that. There was a typo in what I added. Now corrected and we're back to the original result. Logging out redirects to the root page rather than the login screen.

Hi @da² thanks for your thoughts. .htaccess - The .htaccess files is a direct copy of the working one on the development installation (i copied it over earlier today to be sure) so I don't think that's it. 404 in config - there wasn't one in the config file so I added the once you stated above and now on logout I get a redirect to 'mysite.com/admin/login/logout/' which throws a 'this page isn't working' error. That's new so you might be on to something? Hooks - the only hook in the ready.php is the standard one for logging sent emails and that has no redirects in it so I think we can rule that out too :-(

Hi all and seasons greetings! I have a problem that's driving me a bit mad and wondered if anyone in this wonderful community can throw any light on it. I have three copies of the same site, a marketplace where registered users can add listings. The copies are localhost (on MAMP), development, and live (www). All copies are running: PW 3.0.229 PHP 8.08 All copies are also running a duplicate set of /site/ and /wire/ files. The live and development copies are running on the same server. On one copy of the site (annoyingly the live one...) I cannot access the admin login page directly. I have '/admin/' setup as the admin page. Whenever I try the url - 'www.thesite.com/admin/' it diverts to the root page of the site 'www.thesite.com'. As it's a marketplace, I can access the admin by first using the 'public' login screen for members then pasting 'www.thesite.com/admin/' into the URL bar. This redirects to www.thesite.com/admin/page as you'd expect. When I logout again the system diverts to the root page of the site rather than the admin login page. Since I can login on the user facing login page, and the logout function diverts to the root of the website rather than the admin login page, I'm thinking the issue is with the login page / login process. I'm not familiar with how this works but I have compared the /wire/Modules/Process/ProcessLogin/ folders and they look to be the same (and file sizes report the same). I should also say that all other admin functions work fine once logged in. The only difference between the three sites I can think of is the database as the live one has all the latest listings in etc. Does anyone have ideas as to what might be causing this, or could explain how the login process works? As always, any help is really appreciated!

Many thanks @gebeer for this. Some of what is needed could certainly be handled by the page tree. I hadn't tough of that. However, I think I'll also look through the URL hooks idea as that might be the only way to handle some of the more complex issues.

Hi folks, A lovely client of mine is looking to extend their PW site to include region or 'locale' specific content (e.g. a differently laid out home page, local product prices etc.) for certain world regions. These would be chosen by the user from a header menu and the choice retained for a sensible amount of time. The site already has languages presented using the native PW language functionality so their current URLs are in the form mysite.com/fr (using French as an example). We have discussed some different ways of handling the locales. We have ruled out out subdomains for obvious maintenance and SEO reasons. The next thought was browser cookies. However, if possible I'd like to handle the locale specific content server side if possible, rather then sending it all to the browser and using JS or similar to show the content for that locale. One question they have asked is 'can we use and additional URL segment to achieve this'? This would enable direct linking to a specific page / language / locale. For example, French speakers in Canada could use 'mysite.com/fr/ca' or 'mysite.com/ca/fr' (we don't mind what order the language / locale appear if that matters). Has anyone come across / found a solution for this type of question? If so, how did you handle it? Or, is there an alternative solution for this that I'm missing? As always, any and all suggestions / thoughts welcomed and appreciated!

Hi Robin, actually this solves the issue nicely going forward. Thank you.

As part of site development I somethings need to change crop sizes / settings in the codebase after the client has started to add content. This means I can end up with a lot if image variations having been created (and still being used) but with old settings. A good example might be an image variation that was created using a quality of 50 but now the code is set to 100. A new variation is not created under these situations, only if the variation size is changed. So, is there a way to purge all variations leaving the original uploaded image so new variations can be created at page runtime? I have tried the 'PageimageRemoveVariations' module (later v4 version) but that doesn't seem to remove images that are in repeater fields or RepeaterMatrix fields. I'm guessing a solution might have to work at a file level rather than field level? Any help here would be appreciated!

Is there a way to configure this module so that a 'no cookies at all' options is available? This would need to mean the wire cookies are also not loaded. Asking for a client!

Thanks for your help @ryan. I checked the admin template and segments were not allowed (I assume this is the default as I didn't even know this section of admin existed)! I also checked my MAMP copy of eth site and that does not have segments allowed either and that's working fine. I've allowed segments on the live site (the one with the issue, see config image below) but the problem remains: I did look at the browser Network tab and only two redirects were noted (see original post). Looking further at where the issue happens, when I login to the MAMP site (that works) the page you get to is '/admin/page/?login=1'. However, on the version of the site that is live the login process directs you to '/admin/template' which, I'm guessing is where the issue is? Another thing I've noticed with further investigation is that, if I switch to the Reno or Default themes the 'Pages' menu is completely missing. It's there in UiKit but not in the others. Again, checking my local copy of the site, the Pages menu is present in all themes?

Hi folks, PW 3.0.210 PHP 7.4.33 DB MariaDB I know others have had similar issues with this error displaying and I have worked through all proposed solutions (I think....). Here's the issue, on admin login I see this error: Looking at the network tab of browser tools I only see 2 files which are not status 200 when login has completed: I also see the issue when trying to delete pages either via the Lister (Find) or in the page specific admin (example here from Lister after the 'Trash' button is clicked in Pages > Find - note I do not have ListerPro installed). Thsi means I can no longer delete pages in admin! There are no errors in console and no errors in PW logs or the hosting's PHP log file. Finally, deleting pages via the API completes with no issues or errors. To try and diagnose the situation further I have also: 1) Installed a brand new version of the whole 'wire' folder 2) Brought in a known-working, version correct, version of the .htaccess file with only the no.9 'https' directive active. 3) Checked there is a valid 'Profile' page under Admin in the page tree and that page has the correct 'ProcessProfile' Would any of you super people out there have any other ideas I could try to correct this? Thanks in advance!

Hi @BitPoet, Many thanks for this. The $urls->assets issue was the problem here. I didn't understand the difference between this and the $config->paths one so that's something new I've learned. Thanks!