Moving a site up one directory - File Manager directories do not work
Permalink
v8.3.2
I'm assuming Concrete is unable to launch the appropriate java scripts. Any ideas as to why?
I created a new site in a subdirectory, enabled pretty URLs, and just now moved it up one directory. Everything on the public portion of the site appears to be fine.
Clear cache and deleted everything in the cache directory as well.
However, the nicely laid out directory tree in the File Manager does not function at all. The root directories appear, but one cannot drill into the directories. Right-click brings up the context menu, but nothing works. Also, as I have multiple pages of directories, selecting page 2 produces the following:
[deleted because it is not relevant. See comments below]
I'm assuming Concrete is unable to launch the appropriate java scripts. Any ideas as to why?
I created a new site in a subdirectory, enabled pretty URLs, and just now moved it up one directory. Everything on the public portion of the site appears to be fine.
Clear cache and deleted everything in the cache directory as well.
However, the nicely laid out directory tree in the File Manager does not function at all. The root directories appear, but one cannot drill into the directories. Right-click brings up the context menu, but nothing works. Also, as I have multiple pages of directories, selecting page 2 produces the following:
[deleted because it is not relevant. See comments below]
Enabling pretty URLs and then moving a site is a recipe for disaster. Your .htaccess (or equivalent) is probably wrong. A guru might be able to fix it. I'd roll back to the subdirectory version of your site, then disable pretty URLs and try again.
Thanks for the response, I was thinking about that before moving the directory tree. The only difference between the root and the subdirectory is of course the RewriteBase, which just deletes the subdirectory to become "/". And the rest of the site functions. It is just the launching of java scripts. So I am thinking it must be something else, and likely just as obvious.
Frustrating that one receives the exact opposite advice regarding Pretty URLs, depending on which comment thread one follows.
Frustrating that one receives the exact opposite advice regarding Pretty URLs, depending on which comment thread one follows.
Just for kicks I moved the directories back to the sub-directory and the issue with running these scripts goes away. Turned off Pretty URLs, and everything still functions. Moved directories back up to the root (fixing the .htaccess in the root of course and flushing cache), and the issue comes back.
It is like some scripts are just not being loaded, and so functions such as concreteHelpLauncher() or createPseudo() are not being defined. These I guess are java scripts that are loaded differently than those for normal page display, as those function fine. These are for popups and such that Concrete wants to display.
BTW: I can rename the sub-directory and everything still works with no java script errors. I can move the files to a sub-sub-directory and still no problem. It is only when they are moved to the root. I deleted everything else from the root just in case there was some interference, including the .htaccess file with settings for cPanel, with no success.
Does anyone have something to try or any idea?
It is like some scripts are just not being loaded, and so functions such as concreteHelpLauncher() or createPseudo() are not being defined. These I guess are java scripts that are loaded differently than those for normal page display, as those function fine. These are for popups and such that Concrete wants to display.
BTW: I can rename the sub-directory and everything still works with no java script errors. I can move the files to a sub-sub-directory and still no problem. It is only when they are moved to the root. I deleted everything else from the root just in case there was some interference, including the .htaccess file with settings for cPanel, with no success.
Does anyone have something to try or any idea?
Happy endings. This turns out to be a browser caching issue. No issue when the site is moved to an arbitrary sub-directory, just when it is moved to the root. I'm sure some browser expert would know why.
With regards to having Pretty URLs turned on or off (v8.3.2), which several other threads have brought up, it makes absolutely no difference, which makes sense. Either works equally fine, so don't worry about it. I moved stuff around to arbitrary sub-directories, renamed directories, etc. No problems.
So after developing something in a sub-directory, all you need to do is:
1. Rename/Move old stuff out of the root.
2. Move the 4 directories and small collection of files to the root.
3. Delete everything in the application/files/cache directory (even if you have caching turned completely off, stuff is still cached).
4. Insert the Concrete5 section into .htaccess if you have Pretty URLs enabled.
5. Clear your browser cache.
With regards to having Pretty URLs turned on or off (v8.3.2), which several other threads have brought up, it makes absolutely no difference, which makes sense. Either works equally fine, so don't worry about it. I moved stuff around to arbitrary sub-directories, renamed directories, etc. No problems.
So after developing something in a sub-directory, all you need to do is:
1. Rename/Move old stuff out of the root.
2. Move the 4 directories and small collection of files to the root.
3. Delete everything in the application/files/cache directory (even if you have caching turned completely off, stuff is still cached).
4. Insert the Concrete5 section into .htaccess if you have Pretty URLs enabled.
5. Clear your browser cache.
Uncaught TypeError: c.expr.createPseudo is not a function
at app.js:5
at app.js:5
(anonymous) @ app.js:5
(anonymous) @ app.js:5
app.js:4 Uncaught TypeError: $(...).concreteHelpLauncher is not a function
at setupHelpNotifications (app.js:4)
at Object.start (app.js:5)
at HTMLDocument.<anonymous> (search:828)
at o (jquery.js:2)
at Object.fireWith (jquery.js:2)
at Function.ready (jquery.js:2)
at HTMLDocument.B (jquery.js:2)