Question [Merged topic] Joomla 1.7 and implications for Kunena

LN888 wrote:

Estacey2009 wrote: Is it ok to press the button?

I just gotten Akeeba, and WOW that thing is skookum! the only thing is that I don't know how to make it CREATE a restore point. I did a total site backup, and I see the section for restore points, but none were made yet, and I cannot figure out how to force it to make one. I guess it just does it on it's own. I will learn more as I go.

Cheers

Akeeba Backup (as well as Akeeba Admin) comes in two flavors.. Free to use, and Pay to Play.. The pay for (reasonably priced) version contains more options to manipulate the backup, etc.. etc.. Akeeba will make it's own 'restore points' as you add or subtract components, plug-ins, etc..
This can be annoying if you were say, 'entering all the plugins for jomsocial'.. because about every third plug-in, Akeeba will do a 'restore point' which is supposed to be just an addition to the last back-up, but takes a couple of minutes depending on your server speed... Which, having Akeeba do a 'server' check is the very first thing you should do.. At any rate, you can (but it's not recommended) temporarily revert back to the standard component install.. I'd only do that if you knew what the plug-ins you were installing might do to the entire system!

Some servers may not be as friendly... Caveat!

On the subject of, "The Button".. no, there's been no sign of 'automatic' backups yet, but there has been (even in Akeeba) of notifying the user that an 'upgrade' is available and 'there is the button!' to automatically do so.. of course we'll have to live with the 'nag screens' telling us there's an Updated Joomla and a constant vigil of 'not pushing the button' until the right time..

Which you update first, the component or Joomla will probably be a in the instructions.. Joomla may replace a file you recently added to say, Kunena.. or visa versa..

Another place to be wary of "The button" in your Cpanel... If you used your cpanel to install your Joomla, you may get notice of an upgrade available through your cpanel..

Enough about the button... Beware the button! Get a good back-up before pressing it.

One other scary feature of the new Joomla is that it 'auto-deletes' the Install folder. I don't have a clue why they put that in there, pesonally... I didn't mind renaming the folder and leaving the it there.. But I suspect it's to further 'automate' a 'one-click' Site management era.

Estacey2009 wrote: One other scary feature of the new Joomla is that it 'auto-deletes' the Install folder. I don't have a clue why they put that in there, pesonally... I didn't mind renaming the folder and leaving the it there.. But I suspect it's to further 'automate' a 'one-click' Site management era.

That's not all the way true, from what I found out when I was messing with it is that when the installation screen telling you to delete the installation folder comes up, you have that point and that point only to rename it.

On the first attempt when i hit delete it renamed it "installation to delete #". After that if you rename it, even with an ftp, joomla will rename it "installation to delete #" again all by itself. One other annoying thing that it did was that it will reset your config.php permissions to 444, even when changing them with an ftp or cPanel file manager. This all may have been a weird bug or something with my server, but the installation never did auto delete.

issues from yootheme is simply to resolve, only a change on the menu core make trouble with J1.7
before it, menu have an id as attribute, now it's a class...

for all warp theme modifing this file:
theme/warp/systems/joomla1.6/menus/pre.php at line 41
replace this line by
for kunena maybe the issue is about the new location of some files, of course the version.xml is one of them

I understand that 1.6.5 will be released when its ready, but as Joomla 1.6 all versions has many security issues, it can't be recommended keep using em.

Only way is to update to Joomla 1.7.0 and take forums offline until kunena 1.6.5 is released unless you like to give open doors for hackers :dry:

Here is more info about Joomla security vulnerability
developer.joomla.org/security/news/357-2...s-vulnerability.html
yehg.net/lab/pr0js/advisories/joomla/cor...e_scripting%28XSS%29

Joomla! 1.6 is still supported until mid-august, so i hope that there will be a Joomla! 1.6.6 to fix that

rich7424 wrote:

Estacey2009 wrote: One other scary feature of the new Joomla is that it 'auto-deletes' the Install folder. I don't have a clue why they put that in there, pesonally... I didn't mind renaming the folder and leaving the it there.. But I suspect it's to further 'automate' a 'one-click' Site management era.

That's not all the way true, from what I found out when I was messing with it is that when the installation screen telling you to delete the installation folder comes up, you have that point and that point only to rename it.

On the first attempt when i hit delete it renamed it "installation to delete #". After that if you rename it, even with an ftp, joomla will rename it "installation to delete #" again all by itself. One other annoying thing that it did was that it will reset your config.php permissions to 444, even when changing them with an ftp or cPanel file manager. This all may have been a weird bug or something with my server, but the installation never did auto delete.

Thank you for that update on that feature, I had not installed J1.7 using the upload files method.. I was only basing my comments on the material on Joomla's site. Question, what's the difference between renaming a folder (and 'auto' renaming it) and deleting it? You say you cannot rename the folder to "install", Joomla 'auto' renames it?

Changing the folder permissions on a server can result in some pretty hairy events. I've actually been locked out of folders on my server.. couldn't reset the permissions.
It may have only been a fluke on your server... But consider Joomla changing the persmissions to a folder Kunena uses.. effectively locking that extension out.

At any rate... with every tick of the clock, we're discovering J1.7 (and into 1. are giving the community fits.

Makes you so paranoid that you're checking your error log again and again.. what a shock when you see that it has swollen to a confusing, 'where do I start to fix this' file.