X3 Photo Gallery Support Forums
Not sure what config file you have changed. You should NEVER be editing any config file manually, and it seems like you have edited the wrong one ... The warning you are looking at simply tells you that you should change the login to your panel, since it is using the default admin/admin. It even says "Please go to X3 Panel › settings › panel, and change the username- and password to secure your website.", including a link to the panel where you can login and change it.timberline wrote:Ive installed the new version and even went in and changed the config file and resigned in to the panel.
And this you have done? It is not clear to me, as you said you have edited the "config file", and Im not sure what config file you have edited. I really need link to your gallery to diagnose this, as the screenshot just says what it sees,timberline wrote:But it wont show anything on the settings page and it keeps telling me "It seems you are using the default Panel login. Please go to X3 Panel › settings › panel, and change the username- and password to secure your website."
It seems you may be misunderstanding something. The top part says there are no critical issues to run the gallery, because there aren't. The bottom part is a WARNING that you should change the admin login. I don't see how this is impossible ... You login to the panel, and navigate to the settings page in the panel. Where does it say you have to fix the bottom issue before it can even show the settings page? You can login to the panel with default admin/admin, view settings, and change login ... that will solve the warning.timberline wrote:But then the top part says "There are no critical issues, but we recommend resolving warnings if possible. Once satisfied, you may proceed to Panel › settings › settings and disable diagnostics." Which to me seems like its impossible if the bottom part is telling me to go to the settings page and the top part is telling me i have to fix the bottom issue for it to even show the setting page. Just wondering how to handle this?
Sorry, the "x3docs" you are looking at, are outdated, and therefore we have removed most references to these temporary beta docs for an earlier version. I am wondering though, when you first got the diagnostics, it clearly says:timberline wrote:I went by this link that says you should change the config file. (https://www.photo.gallery/x3docs/setup/panel/) that's why i opened and changed the config file. After I changed the config file it let me sign in under my new name and password.
warning wrote:It seems you are using the default Panel login. Please go to X3 Panel › settings › panel, and change the username- and password to secure your website.
It is likely that something is broken after editing config file directly. The warning still shows up in diagnostics, because it thinks the user/password is still default, because it is likely you have edited panel/config.php directly instead of the actual config user file.timberline wrote:My problem is that i have no appear on my settings page it is just blank so i cant do anything on it. I have went to the protect page and added new users and changed the config file for users. But that warning is still coming up to go to the settings page and change users and password to protect my site but when i go to settings this is all i see.
Well, if you can't get to the settings page because of an error, then obviously this needs to get solved first. I would imagine this error happens because of your custom config editing to be honest, so I would revert back to the original X3 files before anything else (please never edit any config files manually). I can check for you, but will need panel login (or send me link before you change it from admin/admin), and possibly FTP (unless it gets fixed automatically by reverting to original files).timberline wrote:There is a very good chance I've missed something or misunderstood something before this step but at this point Ive tried it twice and had the same problem both times. That it tells me I have to go to the settings page and secure my website and then it says i can satisfied doing that i can proceed to the panel settings page and disable the diagnostics but if i cant get to the settings page how can disable the diagnostics.
Sorry, the "protect" area is only for protecting pages in your X3 website (frontend). It doesn't affect login to the panel in any way. Panel login is set in settings.timberline wrote:I can go to the "Protect" area in the panel and make & save changes but when I try to login I get the same default login.
Just to clarify: You have to make admin password setting changes in the "Setting" and not in the "Protect" area? If this is correct then you can see that I can not get to "Setting".
No problem at all. It is understandable if you are confused, as the server issues have broken much of the expected functionality. It's an opportunity for us to implement better diagnostics and fail-safe some issues.timberline wrote:Thanks, Sorry to be such a bother
Yes you are right that the main focus is around Linux->APACHE server, since 99% of public hosting services use this (unless requested otherwise). Technically, X3 should work properly under windows also, as long as PHP is operational, but there are a few crucial factors that we have not yet been able to address. Most importantly, there is a crucial .htaccess file (apache/linux), which X3 depends on to rewrite pages and create "nice url's", and also for calling upon resized images. I apologize that you were not notified about this previously, as I should have noticed it when diagnosing.timberline wrote:I see that much of the documentation centers on Linux as well as things such as modules specific to Apache rewrite, deflate etc. . . Is x3 supported using IIS on WIndows? If it is can you provide any guidance or documentation that could help me to ensure all of the appropriate settings are configured and pre-requisite software is available?
Yes. Generally nothing wrong with this aspect. I see your host was using PHP 5.3.6, and it would definitely be better if you were using version 5.4 or higher ... There are some issues with 5.3 regarding encoding and a few missing features.timberline wrote:1 - The server has various versions of PHP installed to support older software including some older Imagevue. However we have the newest PHP clear back to the older 5.3. All we need to do is configure the individual site for the desired version of PHP. This is done.
Ok. The server should definitely be serving all typical web-formats though ... This is crucial to ANY web application. I don't see why any web server would not serve json files by default, unless it is a custom server setup from scratch (which means problems).timberline wrote:2 - The JSON files are not missing. JSON isn't a file type served by IIS by default. This was easy enough to fix.
Yes, it should be the only issue to deal with ... There was another warning on your server: "Warning: filemtime() [function.filemtime]: stat failed for ./config/config.user.json", but this seems related to the JSON file compatibility. Also, there seems to be a problem with UTF-8 character-encoding, and I was thinking that could be related to php 5.3 ...timberline wrote:From what I can tell the primary issues for IIS are the URL rewrites and the htaccess.
RewriteEngine on
# Customize what Apache returns to the client in case of an error.
ErrorDocument 404 /404.html
# Rewrite any calls to *.html, *.json, *.xml, *.atom, *.rss, *.rdf or *.txt if a folder matching * exists
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !public/
RewriteCond %{DOCUMENT_ROOT}/public/$1.$2 !-f
RewriteRule (.+)\.(html|json|xml|atom|rss|rdf|txt)$ $1/ [L]
# Add a trailing slash to directories
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !(\.|\?)
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ([^/]+)$ $1/ [L]
# Rewrite any calls to /render to the image parser
RewriteCond %{REQUEST_URI} render/
RewriteRule ^render/. app/parsers/slir/ [L]
# Rewrite any calls to /* or /app to the index.php file
RewriteCond %{REQUEST_URI} /app/$
RewriteRule ^app/ index.php [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)/$ index.php?/$1/ [L,QSA]