Hi - I've just successfully upgraded a site from J 2.5 to J 3.3.6 but in global config the paths to log and temp folder are still linking to the development folder i.e. public_html/newsite.
There are probably other bad links as well.
I seem to remember there was a way to fix this globally, but I can't remember how.
Has anyone any suggestions?
Thanks
Ian

Hi Ian,

You can change the path via the backend of the site as well as editing the config file

There are options in admin tools as well - can't remember if there is anything for the log file

Cheers
Paul

Ooops - I removed 'newsite' from the temp and log paths via the back end. shouldn't have done that. I've lost the database:

Error displaying the error page: Application Instantiation Error: Could not connect to MySQL.

Now I'm panicking!

There is a reference to 'newsite' in .htacces:

##### RewriteBase set - BEGIN
RewriteBase /newsite
##### RewriteBase set - END

Not sure what to do now...

Thanks

Ian

Hi Ian,

First edit the config file via downloading it via ftp

I'm not sure what you mean to do with the re-direct but you can just comment it out

Cheers
Paul

Hi Paul - thanks for getting back to me, and sorry for the delay.

I've downloaded config.php - do I just add 'new site' back in from where I deleted it?

Thanks

Ian

Hmm. Tried that, no joy.

Any ideas?

Thanks

Ian

Hi Ian,

The paths have nothing to do with the database.

You need to check the $db $dbprefix $host $dbtype $user $password variables and make sure they are correct for your database access information.

The path to the tmp folder is needed when installing extensions. You need to get the root path to your site from your hosting account and correct it there.

Regards,

Rob

Hi Rob - thanks for getting back to me.

I'm a bit out of my depth here, but not a great problem because I have a recent back up, and with luck I won't lose too much if I revert.

However, I'm puzzled by what went wrong and it would be good to understand. I'll tell you the whole story…

I updated from J2.5 to 3 in a sub directory '/newsite'.
Once approved I put the old site into a directory called old, and put the new site into public_html.
Then in global config I set rewrite urls to yes and the site broke (I did have .htaccess).

I saw that the temp and log directory paths were still set to /newsite, so in the back end removed /newsite from the path.

I was also aware of the .htaccess redirect to RewriteBase /newsite - although I don't really understand this.

Refreshed and got this, both front and back ends…

Error displaying the error page: Application Instantiation Error: Could not connect to MySQL.

I've not changed anything - as far as I'm aware - except the paths to log and temp, so don't understand why it went wrong.

I've attached configuration.php and .htaccess for you to have a look at…

It would be great if you could shed some light - as always it's probably my user error.

Thanks

Ian

Hi Ian,

Changing the path cannot cause that error. It simply means that Joomla cannot connect to the database.

As the database settings are also in global configuration, they might have been changed accidentally or by a browser autofill before saving the settings.

You need to open up the configuration.php file and check the variables mentioned above contain the correct information to connect to the datanase, eg:

Hi Rob - thanks for this.
I went through configuration.php and the database username had changed - I have no idea how or why.
I corrected it and replaced the corrupt file, but still no joy.
I then extracted the backup jpa file, and replaced configuration.php again (the file looked right to me). But still no joy.
I've checked and repaired the database in cPanel, but that had no effect either.
I'm clearly missing something - what should I do next?
Thanks
Ian

Hi Ian,

All I can say is that the database connection information is wrong and Joomla cannot connect.

I would first double check the settings and if they look to be right, maybe use a simple php script to see if that can connect with the same details.

You coulds also try resetting the password for the database.

I think the best option if none of that works would be to contact your host and get them to check on the situation.

Regards,

Rob

Hi Rob - thanks for getting back to me. I'm beginning to panic a bit!

I have asked the host, and I'm waiting for a reply.

Meanwhile, would it work if I created a new database, restored the site from akeeba backup file, and entered the new database details at the setup stage?

Thanks

Ian

Hi Rob - support at the host managed to get into configuration.php and the home page is back, but all the links in the site appear to be broken.
Could you possibly have a look and let me know what you think.
I can get into the admin area, and have tried updating the links, but without any joy.
Thanks
Ian

Found it! I turned off use url rewriting, and everything came back.
Thanks to you and Paul for all your help on this one.
I've now got to sort out why url rewriting is not working.
I'll start another thread if I need more help on that one.
Thanks again,
Ian

Hi Ian,

Thanks for the update - good luck finding the issue in the htacess file

Cheers
Paul