cwsoft

You need to contact your ISP to sort out if there is a way to set the required file/folder permissions the way required to setup PW on your shared host environment. Maybe read this tutorial on securing file permissions too https://processwire.com/docs/security/file-permissions/

I don‘t know the outdated module and how it stores text and maps that to images. From your first table, one sees some null values for gif images but not for jpg for example. When did the issues start? Have you or your ISP upgraded the PHP version used etc. Is it really needed to remove the module or could sorting etc. be fixed by fixing the module? Have you checked error logs and enabled debug mode (e.g. on a localhost copy) to better spot the error? How far are you in the process of implementing the old module just with core functions? Have you tried to e.g. loop over the gallery pages and extract the images text into a textfile or CSV by using the PW API e.g. from a custom template file etc.?

@biberI am not the one you need to convince. It‘s your data and you can do with your database whatever you like. I was just puzzled by what you want to achieve or whats your problem is or if there is any at all. All still not very clear to me to be honest. What caught my attention was that I got the impression that you wanted to alter the text representation in the database, as the database values don‘t show up UTF8 chars but store German Umlauts in an encoded representation. Thats where my advice came from, not to alter or manipulate DB charset/collation manually, if text shows up correct in the frontend. Doing so will most likely corrupt your database and you need to go deep inside the rabbit hole to get charset/collation and data right. Of course you can modify, copy, rename or delete fields with PHPMyAdmin or from the Adminer module from the backend. Adminer is part of the Tracy Debugger module for example. However, for me it‘s just not clear, what you try to do and why it‘s necessary to do. If it‘s just for experiment, than I would just go with phpMyAdmin or Adminer and change some content and see what happens. By the way. I write most of my websites with plain HTML5, CSS3 and vanilla Javascript/Typescript and or PHP 8. Just for projects with multiple users or changing content, I prefer Processwire CMS/CMF which saves me a lot of work. However in those cases I rely on the PW core and API and only modify/dig deeper into the core or database if there is a real need for me to do so.

@adrianGood point.

Have you tried to upload a clean fresh PW installation with a basic or blank profile first or did you try to upload an older existing PW site? Have you followed those steps https://processwire.com/docs/start/install/? Sounds like a file/folder permission issue for me or maybe an broken upload with your FTP tool. Some infos about file permissions can be found in the tutorial section too https://processwire.com/docs/security/file-permissions/.

I would never change or modify the database directly unless there is a real need to do so. If the frontend is not broken (e.g. German umlauts displayed correctly, images show up etc.), I wouldn‘t touch the database at all. If you want to get a deeper understanding than create a local copy of your site and give it a shot. Checked some pages in the frontend and umlauts are displayed correctly so there is no need to change the values stored in the database at all from my point of view.

Guess one part of the story is that pagefileSecure relies on .htaccess available on Apache servers. So it won‘t work on NGINX powered servers unless you port the htaccess over to NGINX equivalent - if possible at all. As htaccess can inherit rules from parent folders and can be disabled from your ISP, it is good practice to test htaccess access restrictions before it goes live.

😀

Wouldn‘t it be possible to add this as a module dependency to my own modules if JS-Hooks would be a released module on the PW module store? Maybe this would be the first step for other module authors to try out the module and to see if others would adopt using it.

Have you asked the provider if sending mails via PHP mail function respective system call sendmail (Linux) is supported/enabled and what kind of settings may be required? Perhaps they deactivated sendmail etc.

Have you tried sending email via SMTP? Had a similar issue on one site. After switching to PHPMailer with SMTP, sending emails worked. Also ensure the from email uses your domain name.

Dear all, congrats to the redesigned website. Was a big surprise today and first thought, hey what happened to my browser bookmarks, it‘s not PW. But that shock only took a second then I realized it‘s my CMS of choice, just with a new fresh layout. Great work from my point of view. Just browse and read the new content now. Love it.

My debugging solution depends on the PW and PHP version I am one. In your case I would first try to upgrade the PW core with the latest version from the master or dev branch. For that I upload/copy latest wire/ folder with all files and subfolders to my site as wire.new/. Than I rename wire/ to wire.old/ and wire.new/ to wire/ and reload the page. Then I login to the backend and reload the admin and modules 2-3 times. Next I would check the logs and see if that already solved the issue. https://processwire.com/docs/start/install/upgrade/ If that doesn‘t solve the issues, I would install Tracy module and dive deeper into the issues. But before I do this, I always ensure I am on latest PW core with the recommended PHP version for the core version.

I want to share another function-alias (.bash_aliases) I use quite often when dealing with DDEV and composer on my Windows WSL2 setup. I usually install PW via GIT and add 3rd party composer packages into site/vendor instead of PW root. function ddcomp() { if [ -e "$PWD/composer.json" ]; then WORKDIR=$(basename $PWD) ddev composer --working-dir="$WORKDIR" "$@" else ddev composer --working-dir="." "$@" fi } The alias-function ddcomp checks if the actual directory you enter the command contains a composer.json file. If it does, it assumes the base folder (e.g. site) as --working-dir for composer. If there is no composer.json file, the actual dir is used instead. This way you can type e.g. ddcomp config --list inside the PW site folder containing the composer.json file instead of using ddev composer --working-dir=site config --list. For setting up PW from scratch you can use ddcomp create-project processwire/processwire.

Required something similar some time ago. Maybe this topic is helpfull for you. Be aware that basic auth can be switched off by group policy rules in Windows by system admins. In this case the user will only see a forbidden page and no login form at all. Thats why I finally added a frontend login via PW API myself, which worked just fine.