Hi Kori! Thanks a ton for your insights! I've looked into everything you mention...
Quote from: frogabog at Aug 17, 2016, 04:31 AMMODX's default "page not found" is always ID 1 unless you change that in the System Settings. Typically, you'll want to make an Error Page resource, and in System Settings change the ID to your new resource (page).
This makes sense. I made an Error page and set the ID in system settings.
Quote from: frogabog at Aug 17, 2016, 04:31 AMThe gallery.html page... did you install Gallery from Extras? I haven't used Gallery in years, but some Extras do create resources upon installation.
Nope, I just used the name "Gallery" for a chunk. But "gallery.html" doesn't have anything to do with that chunk. "gallery.html" now gives the error page! =)
Quote from: frogabog at Aug 17, 2016, 04:31 AMThere is also a system setting for a default template, you may want to check that it's set to the one you want to use as default.
Checked! Set at 1, which is what I'm using.
Quote from: frogabog at Aug 17, 2016, 04:31 AMAs I read through this thread, I haven't seen that you've cleared the core/cache files. This would be something to do first when issues like this occur. You can do it by actually deleting all the files in the core/cache folder or my favorite shortcut to opening up the file manager is using Bob Ray's CacheClear snippet http://bobsguides.com/cache-clear-tutorial.html
Yes! I think it was definitely a cache issue. The weirdness came back again last night and then fixed itself again. I deleted all the cache files in core/cache and have not had any problems since. That will be my new go to. Is there any reason not to just delete those files, as that's super easy for me since I always have a file manager open. Also, I thought this is what I was doing when I went to Manage, Clear Cache in the manager. If that command doesn't clear core/cache, what
does it do?
Quote from: frogabog at Aug 17, 2016, 04:31 AMI'm going to second Bob's suggestion to not use Softaculous for installing or upgrading MODX. Really, it's only caused me pain and agony. Something's always not right. A major issue has been database collation. It's good that you've reinstalled (mostly) manually using the UpgradeModx tool but I feel that using it without following the full upgrade process could be an issue (I'm a 'lil paranoid. I also like to do upgrades old school style and just extract MODX.zip on the server. It's not exactly difficult or time consuming). So even if I do use it to upload the new MODX files, I also make sure to do all the things such as updating extras and clearing the cache as is found here: https://rtfm.modx.com/revolution/2.x/administering-your-site/upgrading-modx
I think you're saying that I should follow the Pre-Upgrade Checklist on that page before using Bob's Extra, if I don't do the whole thing myself manually? It says to "flush sessions." I see a Flush Permissions option - is that what is meant?
Quote from: frogabog at Aug 17, 2016, 04:31 AMAnother thing to consider is your rewriteBase in .htaccess. It appears that this domain is a subdomain or is living in a subfolder of a WP site, no? If so, make sure to change:
RewriteEngine On
RewriteBase /
to
RewriteEngine On
rewriteBase /subdomain/
(not sure how a subdomain (or site located in a subfolder of public_html) would even work without that but it's worth a mention)
The thing is, weirdness happens if I put the subdomain in the path. The page will initially load fine with or without that. BUT,
with the subdomain, I start getting 500 Internal Server Errors as I click around in the page. That doesn't happen when I leave it out.
Quote from: frogabog at Aug 17, 2016, 04:31 AMI'd also suggest checking your configuration files for the correct paths. If you look about half way down on this page, there's a list of them. These also should show your subdomain/subfolder in the path. Make sure that the full path to the MODX installation in the subfolder is set correctly in all the files. https://rtfm.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server
Well, these are what you would expect. For example:
$modx_base_path= '/home/possibil/public_html/thetaooftype.com/';
$modx_base_url= '/';
Which might be why "RewriteBase /" works while "RewriteBase /subdomain/" does not.
This morning's weirdness -- what's left over from yesterday is the following. At some point yesterday afternoon, I noticed that the title next to the icon in the browser tab was showing [[*pagetitle]]. I changed this in the <head> of my template (which is used for all current pages) to <title>tToT</title>.
All the pages updated to this except the Contact page. It still shows [[*pagetitle]]. I can't figure out how this could be, when all the caches have been cleared multiple times by now, and [[*pagetitle]] is no where in any of my current code.
The link to the contact page is in the template. Another strange thing is that if I click the link to the Contact page from the main page, it takes me to the contact page. I click the link to the Contact page from the contact page, however, it takes me to the... main page?! It sure does seem like the contact page is using a different template! But from looking at the page in the manager it is set to BaseTemplate like all the others.
Thanks again Kori!
[ed. note: juliehoy last edited this post 7 years, 8 months ago.]
