Support

Site Restoration

#20451 after installation k2 not listed under components menu

Posted in ‘Site restoration’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

PHP version
n/a
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by tampe125 on Wednesday, 09 July 2014 01:23 CDT

sysad@mbd
 Hi - I ran into this issue only with k2 and while looking for a solution, I found this article on joomla forum: http://forum.joomla.org/viewtopic.php?t=809012 which suggested that it could be related to akeeba backup and restoration process.
That made me curious, because I use akeeba and have restored the sites, but in this instance I'm working with a matrix joomla 3 installation.
I checked the database looking for the "0" under component Id vs. menu as the forum post suggested, but I found something quite different (pls. see attached screenshot) - I see duplicate entries of k2 items in menu table.
I have tested it from the scratch: uninstalled k2, deleted the duplicate tables (remaining after uninstalling) - installed k2 again - same issue.
tried again, this time removing k2 + xmap, cleaned up db entries and installed k2 first => OK; then xmap => OK

Somewhat confused, but would like your opinion whether you're aware of this incident and if this has something to do with akeeba.
Thanks,
AZ

tampe125
Akeeba Staff
Hello,

if you take a closer look at the menu items, you will see that they point to different pages. If I remember correctly, K2 installs some menu entries as examples; so this is not an issue, it's how is supposed to be.

Just to be sure, your problem is the K2 menu entry not shown in the backend, under the Component menu, right?
Can you please check if the original site has the menu entry visible or not?
Akeeba Backup simply creates a "snapshot" of the current database state and then dumps it in the new site, there's no logic applied to the database data.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

nicholas
Akeeba Staff
Manager
Since I spent last week debugging this issue, I might just as well chirp in this ticket :) No, Akeeba Backup has not to do with this. This is a problem with Joomla!. I'm not saying "bug" because Joomla! is not entirely at fault here.

We are able to reproduce this issue for any component installed on a Joomla! 2.5/3.x site upgraded from an earlier version of Joomla! using jUpgrade (and probably SP Upgrade, we didn't try that one). The problem is that jUpgrade screws up the IDs and aliases of the #__menu table. Joomla!, namely the adapters of JInstaller, look for very specific IDs and aliases of the parent menu items under which the new menu items will be added. Since it cannot find the parent items it creates a "hanging" and unpublished menu item node. The same applies for overwriting the menu item nodes when you update a component. JInstaller can't find the original menu item and all hell breaks loose.

I spent five hours last week debugging and stepping through that part of core Joomla! code, I am 99.9999% sure of what I'm talking about. I'd say 100% but I will leave the one in a million chance of something else going on.

With your permission I'd like to make this ticket public. I don't want people to rely on inaccurate Joomla! forum posts. Moreover, I would appreciate it if you could post on that J! forum thread and tell them what exactly is going on. I am not going to do that. Last time I tried to prove I'm not an elephant on that forum I was met with hostility. Since then I decided to never reply anything to anyone in there.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

sysad@mbd
thanks Nicholas - here is little bit of my investigative portion, perhaps you find it helpful:
I have started with clean installation of J! 3.3.0 (May 11, 2014) to create my 'matrix' J! v3.x to replicate in the future. I have installed the basics: akeeba tools + backup + xmap + sh404sef + (for the first time) k2 - then in version 2.6.6
I have not noticed immediately that the k2 menu is missing under components list menu. This came to my attention after replicating the site into new installation. After taking the steps back, I have noticed that this issue already exists in my matrix.
What Davide has mentioned, would make sense, except after uninstalling k2, one set of the k2 menu records was still present in the db table.
For what is worth: after cleaning up the db and uninstalling k2 + xmap (this one has a k2 plugin) I have installed FIRST k2 and then xmap - and the problem did not occur. When I tried the same situation in the opposite order (xmap first, then k2) I've got the conflict.

I have not done any sophisticated debugging, but logically, these findings do not point to akeeba, so I was surprised to see the forum discussing it (but, well, you never know - no one is perfect, right? :))

I'll be happy to post my findings and point to this ticket - would you please obscure the db prefixes from the image I posted with the ticket?
Thanks,
AZ

tampe125
Akeeba Staff
I deleted your attachment, so there aren't anymore any personal information about your site.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!