Thread

Hi there,

This is for a site that was working w/o an issue for a while, where the client just reported what looks like an odd series of issues:

Issue 1
Biggest is that the Edit Weblog Entries does not work (screenshot attached). Both filtering by weblog dropdown menu nor keyword search results in a doubling up the header portion.

Issue 2
I thought this may be solved by simply upgrading the system to 1.7.0. However, when I was backing up the site by exporting/importing the database to a separate test domain, the PHPmyAdmin throws up an error (screenshot attached). I’ve held off upgrading until I know better what’s causing the mySQL error.

Issue 3
I also tried to offer the client a workaround and simply use Brandon’s Editor extension. Then I find out that the control panel URL is not being saved at all (screenshot attached).

—-

All of these issues seem related—any help would be greatly appreciated, as always 😊

Jae

The live site, which doesn’t have an issue on the front-end, is http://www.damonrunyon.org

There’s also another issue:

Looks like no information is being saved when editing a page or publishing a new page. It simply kicks you out to the control panel homepage w/o data being saved.

Also found out that

1. host has been down a few times and may have caused a corruption in data
2. client had hired a 3rd party developer to add a form (or other items) which may be interfering with EE

Jae

Hi, Jae.

We can’t help troubleshoot problems with third party addons. About the only thing I can suggest trying is to turn off all extensions globally (by clicking the big green button labeled Disable Extensions) which will disable all extensions without removing their data.

If you do that and the problem goes away, then you’ll need to examine what’s not working well with others.

Upgrading to 1.7 which would be a good idea isn’t going to help with incompatible extensions.

Does that help?

Hi Sue,

Thank you for the reply. Yes, I did disable all extensions (won’t work through CP, so I changed the config.php file’s $conf variable to ‘n’.

The issue still is there—when you use the pull down menu or enter a keyword and hit “Search”, it simply kicks you back out to homepage, although the doubling up of the Edit screen does not happen anymore.

Sue, is it safe to upgrade when I can’t import the database into a copy (backup) due to mySQL error? I’m afraid I’ll lose the live site as well (which is working relatively well, at least on the public-side.)

Jae

ej,

Just a little hint here from the outside.
I would not use phpadmin for mysql db backups! It might work OK for smaller dbs, but given the various version of that app and of mysql, etc. I think there are better ways to back up your db!

I assume you have done this already - but make certain you repair and then optimize all your tables in EE or phpmyadmin. The status report you get back should certainly tell you if any tables are corrupted.

As to backing up mysql, I do it this way and it works fine…....this assumes you have telnet access.
1. Telnet or ssh into your computer.
2. Tar the entire directory containing your mysql files - it’s something like /usr/local/mysql/var
then use ftp to download that tar file to your local computer…....
I’m sure you can use other compression methods (zip, gzip) also…..but doing this from a command line is vastly more efficient since web connections (through EE and phpmyadmin) have all kinds of potential problems.

In a pinch you can use a ftp program and download that directory….

Hope that helps. MySQL is pretty bulletproof…...it is pretty unlikely that something is messed up beyond repair there! Perhaps the best course of action is to repair and optimize and then get in touch with the 3rd party writer…and maybe you can turn on some EE or php debugging to see what is happening.

Awesome - thanks Handyman!

Just starting to look at the DB via SSH and see. May be an unescaped
tag or some sort that’s causing havoc.

The exact situation escapes me now, but years ago I had a problem with a table name or naming convention in EE or in mysql somewhere….....
Probably a custom field that I did - or on an upgrade, etc.

there are a LOT of reserved words (words which should not be table names! Probably not your problem now, but they are always good to keep in mind…..

http://dev.mysql.com/doc/refman/5.5/en/reserved-words.html

Thanks for the assist, Craig.

ejaedesign, where are you with this? Any progress?