TOPIC:

Best regards.

I installed Xerte in a subfolder of my website, and it works correctly. I can log in as an administrator and as a content creator with registered users and editor permissions.

However, when I log in to Xerte, it returns me to the tool's installation screen, and unless I enter the correct link to go to the login area, it always returns to the installer. I've already deleted the SETUP folder, but it still returns to the online installation screen.

What should I do to prevent the installation screen from appearing every time I try to log in with a username and password?

Thank you very much for your kind guidance.

I don't understand what is happening at all.

Could you please share the following:

Screenshot if the installation screen
The correct link to go to the login area (you can leave out the domain if you want)

Hi Tom, and thanks for your reply.

Let me explain.

I have my installation in the following subfolder of my website: (website/source)

If I enter the previous path (website/source), the installation process starts, and it shouldn't be like that since I already installed the tool (attached screenshot). Deleting the SETUP folder is supposed to prevent further installation processes. I already deleted the SETUP folder, and the process still continues if I enter that path.

How do I prevent any installation process from starting when I enter (website/source)?

I'm obviously asking this to prevent someone from entering that path and starting the installation process. Of course, they would be missing the installation data, and there's not much they could do, but it's still annoying if someone enters this path (website.com/source) and tries to do something wrong.

Thanks.

This normally can only happen when you moved the installation to another folder. Also, I do not understand how you can still see the installer if you removed the setup folder.

The first item causes a mismatch beteen the actual folder the installation is in and the path stored in the database. To fix this, you need to change the path in the database to match the actual path on disk in the sitedetails table (column root_file_path).

The second issue somehow means that the apache server reads the installation from a complete other disk/place than you expect it to do. So please chack the root_file_path.

Tom