The latest joomla auto update (to 1.5.14) replaced all fo my files (and changed the owner and perms). So all of my css files, favicon, etc were reset to their original states. Luckily, I had it all backed up but I'd like to make sure it doesn't happen next time. Does this happen with every update? How can I change it? Thanks!
edit:
Ok, well, sorry, I figured out part of it at least. I guess that default templates get updated so all one has to do it rename (or copy, rename, paste) the template folder and pick the new one.
I downloaded the joomla turnkey install to test against my own install (much thanks for the opportunity!) and I'd like to confirm a behavior on enabling encrypted logins.
If I enable encrypted logins (after enabling the mod_login module) with the JA_Purity template with the logging level for the ssl virtual host set to 'info' I do not see any ssl requests. In the same configuration with the rhuk_milkyway and beez templates, I get ssl requests but the site does not return to http but remains on https. I have made no further configuration changes.
I have the hardy heron LAMP appliance running in VirtualBox for development, with the network set to bridged.
I can connect to the virtual server just fine via SSH, http, and log into phpMyAdmin as root.
However, I have the MySQL GUI tools installed on my host (Win XP) and can't get them to connect. I can ping the server from them just fine. I tried port 12322 and that didn't work either. Windows firewall is disabled.
Are their other credentials besides root that I should be using to access MySQL this way?
I'm changing hosts to VPS.net. I'd like to use the Joomla Appliance to avoid the server configuration and ongoing security update issues. However, my Joomla site has too many add-ons and existing content for me to want to recreate it step-by-step. While the installation is highly customized, there are no edits to the core files. Will the following steps work?
I've got a Ubuntu-Joomla image running and updated the system. The version Joomla gives is still 1.5.12, and security updates have been applied in 1.5.13 and 1.5.14 (30 July 2009). Is this package patched? Or does it still need updating?