the simplest solution is to reinstall again, this time under

public_html/photography

you will still have your stuff under a separate directory, of course, this being "photography"

Personnally, I use sub-domains for this. Are you the owner of your domain ? Can you create sub-domains ? If so, you do not need to move the folder where your Piwigo is, just direct the subdomain to the correct folder.

Suppose my domain is katrynou.fr, my different sites will be addressed by : forum.katrynou.fr, photography.katrynou.fr, news .katrynou.fr...

Last edited by Katryne (2022-02-21 20:04:02)

ok so today, I am doing some further research into this issue and here are my findings:

Other people have posted on how this is done. For example this one is pretty clear:

https://webmasters.stackexchange.com/qu … g-htaccess

quote:

You do this by physically changing the URLs in your application, not in .htaccess. Once the URLs have been changed in your application, the request is then for www.example.com/page1, the visible URL that is shown to your users (not page.php). You then use mod_rewrite in .htaccess to internally rewrite the visible URL back to the real/hidden filesystem path: /subdir1/subdir2/page1.php. (But I suspect you already know this, since your code is doing the right kind of thing.)

unquote.

ok so I started looking for a config file for Piwigo and I found this:
https://piwigo.org/doc/doku.php?id=user … onf_locale

Since I have local filesystem access on my webhost, I went looking and I see this:
Under public_html/rajdude.com/photography/local/config/, two files exist:
database.inc.php
index.php

However, the file mentioned in the Piwigo article  local/config/config.inc.php. does not exist.
Guessing it needs to be created first.

Anyway, if I look at the  include/config_default.inc.php file, I do not see something which will let me change the URL of the application (Piwigo).

I guess right now it is set to / and I need to change it to /../ meaning down one level?

Can anyone expert in configuring Piwogo's config files please help me here?
Highly appreciated!

Well, yes, it is quite possible to take that subdomain approach also (I think I posted that above)...but it is a personal preference.

But since two people have suggested it here. I went ahead and made a subdomain and pointed it to the correct path on the web server - public_html/rajdude.com/photography/

Piwigo still does not work on that URL! It throws a 404 error.
--------Wait, I fixed it! Had to remove the .htaccess file in there-----
Check it out
https://photography.rajdude.com/
--------Wait, I fixed it! Had to remove the .htaccess file in there-----


BTW, this still works fine:
https://rajdude.com/rajdude.com/photography/

I have contacted the hosting service. They looked at it and said it is not their server problem, they say I need to contact a web application expert to fix this issue :-( That is not possible for me, I mean, this is just my personal website, I am not running a business here.


PS: You recommend using a subdomain, but you are using a sub-directory for your own website. I wonder if the sub-domain option did not work for you?

Last edited by rajdude (2022-02-23 00:25:23)

If with this directory structure
public_html/rajdude.com/photography/
the URL https://rajdude.com/rajdude.com/photography/ points to that very same location then either you have the domain rajdude.com pointing to public_html/ as can be seen also with https://rajdude.com/rajdude.com/ that just works similar (and delivers some index file's content "welcome to rajdude.com"), or you have some weird rewrite in .htaccess that you forgot about. There's no issue that should be fixed on the application level, but your hosting provider is right in that they said it is not their server problem, it is just how you set up things. And likely it's the same for your other domains and they might even be able to cross-access the other domains' directories, which would be bad. You probably have some .htaccess somewhere that redirects https://rajdude.com/ to https://rajdude.com/blog/ while rewriting paths, i.e. https://rajdude.com/rajdude.com/blog/ does not exist or is not accessible.

If you want https://rajdude.com/photography/ then fix your rajdude.com domain setup to point to the correct public_html/rajdude.com/ directory, but be aware that you'll have to change something that so far does the current redirect/rewrite to the blog/ subdirectory.

You could tweak public_html/.htaccess to redirect all https://rajdude.com/rajdude.com/photography/ to https://photography.rajdude.com/ or https://rajdude.com/photography/ or rewrite accordingly, without changing the domain setup, similar to what you did for https://rajdude.com/blog/, but that's a mess.

I might be wrong in my conclusion about your domain setup, but it's the most obvious.