Thread

I went from 1.6.8 to 1.6.9. (Version update)

I’ll run through the Version update again and advise.

If you are saving templates as files make sure to back them up also.

Please clarify the above. (As in, where do my template and css files live?)

Thanks.

You mentioned you upgraded to 1.6.9, but your config.php file still says 1.6.8? Is that file writable?

Yes, should be.

Please check your email shortly.

Hi cfp700,

It looks as though this issue is caused by one of the extensions you have installed. Please try updating them to the latest versions from the respective authors. Additionally, after you upgraded did you replace the config file with a backup from your 1.6.8 install? If so, please replace it with the one from after the 1.6.9 upgrade.

Cheers

Greg

It looks as though this issue is caused by one of the extensions you have installed. Please try updating them to the latest versions from the respective authors. Additionally, after you upgraded did you replace the config file with a backup from your 1.6.8 install? If so, please replace it with the one from after the 1.6.9 upgrade.

Cheers

Greg

Were you able to log into the Control Panel?

It looks like the extensions currently installed are:

ext.cp_jquery
ext.edit_alert
ext.lg_image_preview_ext
ext.lg_live_look_ext
ext.lg_social_bookmarks_ext
ext.tag_submit

Should I delete all of these, and try and install the latest versions of them?

I don’t know that I have config.php file from the 1.6.9 upgrade.

Can you send me a “blank” one and I will update the specific values?

cfp700,

Should I delete all of these, and try and install the latest versions of them?

You should download all the updates for each separate add-on and update individually.  You don’t need to delete original in most cases. Each third-party author will have specific instructions on how to upgrade them.

I don’t know that I have config.php file from the 1.6.9 upgrade.

It would have been the 1.6.8 config.php that was up updated when you upgraded.
Did you drop the 1.6.8 one back in and backup the updated one?

I don’t think I have the updated one, which is why we were requesting a blank one.

Was anyone able to log into the control panel?

Also, what errors were seen that made it look like this issue was related to extensions?

Description of Activities:

Downloaded and unzipped 1.6.9.

Database backed up. Saved path.php and config.php locally.

Extension, language, modules, plugins saved locally, then deleted from server.

EE system folder deleted from server.

Also deleted root/themes folder.

UPLOADS:

The following folders were uploaded via ASCII to my ee system folder (name changed for security)

cache
core
cp
db
dictionary
extensions
fonts (texb.ttf uploaded using Binary)
language
lib
modules
plugins
templates
translations
updates
utilities

I updated the images folders via Binary transfer to the root directory.

I uploaed the themes folder via ASCII to the root diretory.

My path.php file looks OK:

<?php

// ------------------------------------------------------
// DO NOT ALTER THIS FILE UNLESS YOU HAVE A REASON TO

// ------------------------------------------------------
// Path to the directory containing your backend files

$system_path = "./system_folder_name/";

// ------------------------------------------------------
// MANUALLY CONFIGURABLE VARIABLES
// See user guide for more information
// ------------------------------------------------------

$template_group = "";
$template = "";
$site_url = "";
$site_index = "";
$site_404 = "";
$global_vars = array(); // This array must be associative

?>

I edited config.php as follows:

<?php

if ( ! defined('EXT')){
exit('Invalid file request');
}

$conf['app_version'] = "169";
$conf['license_number'] = "7061-4371-8909-WXYZ";
$conf['debug'] = "2";
$conf['install_lock'] = "1";
$conf['db_hostname'] = "mysql123.hosting.hosting.net";
$conf['db_username'] = "$$";
$conf['db_password'] = "*********";
$conf['db_name'] = "$$";
$conf['db_type'] = "mysql";
$conf['db_prefix'] = "exp";
$conf['db_conntype'] = "0";
$conf['system_folder'] = "system_folder_name";
$conf['cp_url'] = "http://firenews.net/syatem_folder_name/index.php";
$conf['doc_url'] = "http://expressionengine.com/docs/";
$conf['cookie_prefix'] = "";
$conf['is_system_on'] = "y";
$conf['allow_extensions'] = "y";
$conf['multiple_sites_enabled'] = "n";
$conf['tag_module_parse'] = "linebreak";
$conf['tag_module_convert_case'] = "y";
$conf['tag_module_enable_tag_form'] = "y";
?>

Namely changing 168 to 169.

I re-uploaded the saved language, modules and plugins folders

Now on to tackle the Extensions:

ext.cp_jquery.php is already there.

Added back the following via new downloads:

Edit alert (ext.edit_alert.php)

Could not get a new file for LG Image Preview (ext.lg_image_preview_ext)
Could not get a new file for LG Social Bookmarks (ext.lg_social_bookmarks_ext)
Could not get a new file for LG Live Look (ext.lg_live_look_ext)

(I have the above three archived, but avoided uploading in case there are errors within).

The only other one I have/had is the Solspace Tags extension. They initially did not recognize me as a user, so I have emailed for download permission.

Do the above steps look correct?

Should I be looking at running upgrade or install next?

I wanted to spell out my steps so far and have you guys take a look before the next action.

Thanks.

Since your database was aleady at 1.6.9 (it was just config.php that said 1.6.8) you don’t need to run the updater. So, delete the system/updates/ directory and system/update.php file from your server.

In config.php I would change

$conf['allow_extensions'] = "y";

to “n” and make sure you can login before extensions even enter the picture.

In my system folder, I now have:

(folders)

cache
core
cp
db
dictionary
extensions
fonts
language
lib
modules
plugins
templates
translations
utilities

and the single file:

config.php

Trying to access control panel I get a 403 error.

Seems like I’m missing some files(?)

Yes, the 403 is caused by the lack of an index.php file in your system directory.

Copy /system/index.php from the EE download package over to /system/index.php on your host. Do NOT copy the index.php from the root folder of the EE package; the two are different. Let us know how it goes.

Finally, a little bit of progress!

I get an unstyle log-in that says version 1.6.9 Build 2010430.

I can log in, and then I get an unstyled control panel.

(this is the first sighting of the control panel in about two weeks, so we’ll consider that a small victory!).

And my templates are still there.

Just to clarify, my themes folder is in the root directory now, not the system folder.

cfp700,

Ok I did as Brandon suggested and changed the allow extensions to ‘n’ and I was able to log in. What I did find was that you server path to your theme folder was incorrect. I have since changed this and now you can see your theme.

Next step is in your config.php file change set your allow extensions setting back to ‘y’

$conf['allow_extensions'] = "y";

When you go back tot he control panel it is going to be looking for the Tag extension. I think you may just have deleted the extension and not uninstalled from control panel. Try uploading it again into the extension folder and see how far that gets you.

Does that make sense?

Yes, makes perfect sense.

If you look at my post #38, I loaded the themes into the root directory. Is that not the correct spot?

I will try and reload the Tags from Solspace and advise.