Yet another problem upgrading to 3.2

[rcannon5]

Earlier today I upgraded Joomla from 3.1.5 to 3.2 through the admin backend. Now, I can't access the control panel and the error

1146 Table 'cannont_jmln1.jml_postinstall_messages' doesn't exist SQL=SHOW FULL COLUMNS FROM 'jml_postinstall_messages'

is displayed. I also can't access the database through the extensions manager. It shows the error

1146 Table 'cannont_jmln1.jml_content_types' doesn't exist SQL=SHOW COLUMNS IN 'jml_content_types' WHERE field = 'content_history_options'

As far as I can tell, these are the only issues that have shown up, and thankfully the front end still works fine. But it is a big problem if I cannot access the backend control panel.

Any help on fixing these issues?

Thanks,
Ryan

EDIT
Just noticed that on the homepage a notice shows up at the top. It reads:

Notice: Use of undefined constant ZHONGFRAMEWORK_PARENT_CMS_RELEASE_CLASS - assumed 'ZHONGFRAMEWORK_PARENT_CMS_RELEASE_CLASS'in /home/cannont/public_html/templates/zhong/application/handlers/cms/cms_components_view.php on line 22

Line 22 of that file is

Code: Select all

if(ZHONGFRAMEWORK_PARENT_CMS_RELEASE_CLASS=="Joomla3"){

[alikon]

i'm afraid that your problem is related from your installed extensions that don't is joomla 3.2 ready

Code: Select all

ZHONGFRAMEWORK_PARENT_CMS_RELEASE_CLASS

is not part of joomla 3.2 code

disable that extension

[rcannon5]

That would probably normally work, but Zhong Framework is my template base so I can't really disable it. Is there any way to downgrade back to Joomla 3.1.5 which was working?

[alikon]

sure restore from backup

[CyberSmyth]

I have had the same database issue on one upgrade to 3.2

I don't use Zongframework so it isn't that.

Everything works except I cannot access the control panel main page.

When I look at the Database in Extension Manager: Check Database I get the following errors


Database schema version (3.1.1) does not match CMS version (3.2.0).
Database update version (${project.version}) does not match CMS version (3.2.0).
Table 'wpzw2_content_types' does not have column 'content_history_options'. (From file 3.2.0.sql.)
Table 'wpzw2_modules' does not have column 'asset_id'. (From file 3.2.0.sql.)
Table 'wpzw2_postinstall_messages' does not exist. (From file 3.2.0.sql.)
Table 'wpzw2_ucm_history' does not exist. (From file 3.2.0.sql.)
Table 'wpzw2_users' does not have column 'otpKey'. (From file 3.2.0.sql.)
Table 'wpzw2_users' does not have column 'otep'. (From file 3.2.0.sql.)
Table 'wpzw2_user_keys' does not exist. (From file 3.2.0.sql.)

any ideas?

[rcannon5]

Well the Zhong Framework template was updated to be compatible with 3.2 so I don't have the issue on the homepage anymore.

However, I still can't access the control panel or the database, the same errors I mentioned earlier are still present.

[CyberSmyth]

After reading the other thread going on about these issues I was able to find the 'fix' button for the database and that seems to have cleared the problem with accessing the control panel. Site appears back to normal (i.e. menu stopped working a while back)

[rcannon5]

It seems like using the fix database button would solve my issue, but I still show an error that prevents me from even seeing the database page.

[JAVesey]

Are you able to login to admin at all?

If so try accessing the page manually:

http://www.yoursite.com/administrator/i ... w=database

[rcannon5]

I can log in to admin, but the error I posted in my first post is what shows on the control panel page. Most of the components are working just fine, with the exception of one which there is an update for I will get soon.

When I tried accessing the database manually the same error message that shows when I go to extensions>database is still there.

[sovainfo]

Advice you to run Extension manager->Discover and install first, followed by ->Database and Fix if still needed.

[rcannon5]

When I go to the discover area, I see a lot of stuff here. Should I install all of it? I do see "Content History" and "Post-installation Messages" which are both components, and those are what the error messages I'm receiving are referencing, it seems.

[sovainfo]

In a properly installed environment there is nothing discovered. Installlation/update installs everything. So, you need to install everything.

[rcannon5]

I installed everything and still no access to the database or the control panel.

[rcannon5]

Correct me if I'm wrong, but doesn't the "Database fix" button run the scripts from admin/components/com_admin/sql/updates?

In that folder, I have a few subfolders, one of which is mysql. Inside that folder are a bunch of .sql files relating to various installations of Joomla. I copied the 3.2.0.sql file to my desktop to see what what inside and the first line contains:

Code: Select all

ALTER TABLE '#__content_types' ADD COLUMN 'content_history_options' VARCHAR(5120) NOT NULL COMMENT 'JSON string for com_contenthistory options';

and below that is a bunch of UPDATE stuff relating to content_history. Near the bottom it has stuff about the creation of #_postinstall_messages. Is there any way I can manually run this script to fix the database because I can't access the database in the Joomla admin?

[sovainfo]

Correction, you are wrong! Database Fix doesn't run those scripts. It runs statements of those script it thinks need running. Those statements are related to the structure of the tables. It doesn't run the other statements because there is no logic available to detect whether they should or not. At least that is the excuse being used. I disagree, they should be run. Just as installation/update is running them. This is also why I advice to run Extension manager->Discover and Install first.

You can start phpMyAdmin and use the SQL tab to run these statements. Don't forget to replace #_ with your prefix.

[rcannon5]

I've been traveling the past few days so I just now got to reading your reply.

phpMyAdmin is in the cPanel, correct? I'll report back with what I find. I haven't been in the cPanel since I installed my website. We'll see how it goes.

[rcannon5]

I believe everything has worked out perfectly! I ran the statements to create the postinstall_messages table and the content_types table to be able to access the control panel and the database. They both worked and allowed me to fix the database.

[juanfer2k]

Are you able to login to admin at all?

If so try accessing the page manually:

http://www.yoursite.com/administrator/i ... w=database

Yes, worked finally!

Fix database is the option, now am running the 3.2.1 version.

Thanks

[chuck-hill]

I believe everything has worked out perfectly! I ran the statements to create the postinstall_messages table and the content_types table to be able to access the control panel and the database. They both worked and allowed me to fix the database.

I am having the exact same problem! Nothing I am doing is working or allowign me to get to Extension Manager -> Database. I would love to try what you did, but unfortunately I am not tracking with you. Could you (or anyone for that matter) shed some light on how this is done? How are these statements ran, where do I find the statements, etc?

Many thanks for your help!!

[gillon red tie]

Have been battling with the whole day as well but finally came right

I went to discover and installed the updates

Then open admin/components/com_admin/sql/updates/3.2.0.sql into your editor of choice and open phpmyadmin at the same time, make sure you are in the right db

in your editor find postinstall_messages - you should end up with this

you should end up with a create table and insert into statements, change #__postinstall_messages to yourtableprefix_postinstall_messages past it into sql tab in mysql and run it

then create the table yourtableprefix_content_types (I just created a dummy row in it) (In my care the table was not there)

Search for content_types in your editor and change the ALTER TABLE sql statement so it has your table prefix in it and run it through the sql tab on phpmyadmin

After these steps you should be able to fix the db

[Zaxxen]

@gillon red tie
Just wanted to let you know that your last post worked for me... and I'm TOTALLY new at databases!

THANK YOU SO MUCH!!!

Happy