floko

@bernhard You are right, I created ready.php with the script lines you suggested and it was indeed executed, including the condition for forceLogin (checked via error_log). However, nothing happened... Thanks anyway for your suggestion! Was worth a try.

Thanks for the hint, @JosephineNeill! I emptied the table session_login_throttle. Besides that, I don't know where to look: table field_pass maybe? Not sure what this does...

@bernhard The salt hash is the same as before, so I can rule that out. Thanks for the hint in any case! Regarding the workaround script to be placed in site/ready.php: Such a file does not exist. Maybe in the PW version I am using (3.0.206) this was not introduced yet?

Thanks, @zoeck! No, I haven't... So I just tried this and added "localhost" to the array. Login is still not possible (also deleted localhost cookies beforehand).

Hi everyone, I copied all root files, /site and /wire content from our live website to a local XAMPP installation, also a copy of the live database dump. Now frontend works fine on localhost, but I cannot login to my admin account. Initially, I received the warning "request was aborted because it appears to be forged" until I suppressed CSRF protection in /wire/config.php Also I set sessionFingerprint = 0 and sessionChallenge to false in config, additionally I deleted corresponding cookies. While the warning disappeared, I am still not able to log in. (Neither do file privileges/permission settings seem to be an issue, as far as I can tell.) Any idea where to investigate next? Thank you!

Ha! That did the trick! ? Thanks a lot! Went through the whole installation process a third time, and now everything worked out fine. The .htaccess file in root now looked *completely* different, must have had something to do with that. ? Thanks again for your help!

I see, thank you! Accordingly, I moved all files & folders up. In addition, I enabled GD library in php.ini (because missing GD triggered a warning during the installation process) and restarted Apache. The standard default home page loads (although it only does so when line 5 in htaccess "require all denied" is commented out) Still I have no idea where to look for the admin section. There is a "/templates-admin" folder below "/wire", so that seems to be a good place to start. I'd expect a "wire/index.php", but there is only an "index.config.php" that obviously is a multi-domain configuration file... Edit: I double checked with the official file structure (listed here https://processwire.com/docs/start/structure/files/). Even there, "/wire/templates-admin" is the only mention of anything admin-related (but only "Templates, stylesheets and scripts for the admin control panel", not the control panel itself). In every install instruction I read, the admin control panel should live in "http://localhost/processwire". But as there is no such folder, I don't get it ?

Hi Jan, thanks for your welcome and your quick reply! /wire and /site are both subdirectories, the structure is /htdocs/processwire-master/... .htaccess is also located within /processwire-master Should I move all files and folders up to /htdocs? Or install everything anew?

Hi everyone, I just installed PW on my old notebook (Win 8.1, fresh XAMPP installed) via the latest master zip package. Worked my way around issues with htaccess (details below*), ignored the missing GD2.0 library and ended up with a working default front end page, but no admin section. The standard link from the last installation page leads to a non-existing URL. I cannot not find any subdirectory called /processwire or /admin to enter the admin page URL manually. There *is* a subfolder called "wire", but no "index.php" therein. Any idea where to look next? Thanks! *htaccess changes: had to remove all restrictive lines from the default .htaccess file before I could proceed with the installation ( "require all denied" and "deny from all").

@Gideon So 4, and all of them require access to the file system in some way: 1) add module from folder/directory (available only in debug mode, requires changes to config.php) 2) add module from URL (same as above) 3) add uploaded module (same as above) 4) add module manually (requires access via FTP client)

@Gideon So Great idea, thank you! Tried immediately, but unfortunately I have limited options to install a new module via admin UI. As far as I can see, adding a module from URL requires changes to config.php beforehand (set debug mode to true)... Thanks anyway for your suggestion!

@da²You are right, it becomes clear that I will need to have access to php files via ftp. Thanks again!

@da² Thanks for your hint! In this case, the child page ("/contact-person") is not directly accessible via admin ui. In the parameters tab, I can only edit the name/url of the course page, not of its assigned contact person(s) page.

@monollonom Thanks for your advice! Yes, "allow URL segments" is checked. As suggested, I added all possible variants to the text area. Unfortunately, this does not change anything. That was definitely worth a try, thanks again ?

Hi @TomPich and thanks for your welcome and quick response! When I change the field content for the title from "contact person" to "contact persons", the link succesfully changes from "/contact-person" to "/contact-persons" automatically in frontend, as does the link text. So that's working as expected. However, when I click/follow the link, a page opens - complete with the usual standard layout and navigation elements of the website, but without the main content defined for that page. When entering the old, former URL (/contact-person) manually, I see that the old content is still there.