installation dir name

I installed C5 in a subdir to public_html. So now I have this structure: public_html/projectname/concrete5.7.5.2/

Everything works, but concrete5.7.5.2 turns up in paths when viewing the source of the page.

So, here are the questions...

Should I have renamed the installation dir after I installed C5? (I'd like to know this since I'll be using C5 more.)

Can I rename the installation dir now? eg, "othername" instead of concrete5.7.5.2 so the path would be public_html/projectname/othername/

Also, can I install C5 directly under public_html and rename it to "projectname"?

I hope it's okay to ask more than one question in a post. If not, my apologies in advance.

Thank you.

View Replies:
MrKDilkington replied on at Permalink Reply
Hi GNUguy,

I just tried doing what you described and concrete5 still works as expected.

Using your example:
- I changed "projectname" to a new name
- I also changed "concrete5.7.5.2" to a new name

You can also install concrete5 in the root:

I don't think there is any harm trying this on a freshly installed site. If your site has content, make a full backup first to be safe.

Also, I recommend using the most current version of concrete5. Which is now
GNUguy replied on at Permalink Reply
Hi MrKDilkington,

I just tried an install to test this myself. Unfortunately when I click submit to complete the install, it throws an error. I've done 4 different installs and this is the first time I've seen this error.

SQLSTATE[28000] [1045] Access denied for user 'username'@'localhost' (using password: YES)

I've just started to research the error, but haven't found a solution yet.

But I really appreciate you taking time to try out the situation. That is really considerate of you to put in the extra effort like that. Now I feel a bit more comfortable making the change.

BTW, I actually am using Just upgraded a couple of days ago. That's another reason I wanted to rename the install dir. And I appreciate you suggesting I get current. One should never take anything for granted.

I have to say, it is one heck of a lot easier upgrading a C5 install than a Drupal install. What a pain that was! Although that was 3 years ago. Maybe they've improved it now.

Thanks for the quick response, MrKDilkington.
GNUguy replied on at Permalink Reply
I tried this out as well. From my example "public_html/projectname/concrete5.7.5.2/," I changed the name of the last dir in the path; ie, "public_html/projectname/diffname/." The site continues to work as intended. However, if you use any "custom CSS" (eg, background images), you'll need to update the path info, as well.

I also just did the recent upgrade to without any issues after I had changed the dir names.

May I suggest an edit to the C5 installation instructions? Perhaps it would be worthwhile to include the fact that a person can install C5 in the root and change the name of the install dir from "concrete5.version number" to a different name (eg, "projectname").

I just did another install of C5 using the approach of installing in the root and changing the install dir name. And after doing that I discovered that enabling "pretty urls" works as intended when C5 is installed in the root. I have three installs where I have yet to successfully enable pretty urls because I took the instructions literally and installed C5 within my project dirs (ie, public_html/projectname/concrete5.7.5.2/). There might be other naive first-time users out there like me who would benefit by knowing about the option to install in the root and help them to avoid the whole "pretty urls" problem that I see discussed so often.

Feel free to contact me directly if you would like to discuss this further. (BTW, my background is in technical documentation; 15 years, 12 of which I worked as a dept manager).

Thanks again for your help, Mr KD.
MrKDilkington replied on at Permalink Reply

This portion of the documentation might also be helpful:
"Moving a Site"

As an open source project, where anyone can add or edit documentation, any contribution to make it better is welcomed. Especially in your case, having a professional background in writing technical documentation.
GNUguy replied on at Permalink Reply
Thank you for the link, MrKDilkington.

I'll check into the documentation effort, as well.
GNUguy replied on at Permalink Reply
Thank you for the link, MrKDilkington.

I'll check into the documentation effort, as well.