Can’t access admin page <div id=error> after upgrading

  • Resolved eastbayinsomniac

    (@eastbayinsomniac)


    17 years, 5 months ago

    I just upgraded after following the instructions on the site. I backed up my wp-content and wp-config and deleted and replaced the other files. I am trying to do the DB upgrade, but I cannot access my admin page anymore. I get an error that I think relates to a table in a plugin? But how can I deactivate a plugin if I can’t login to my admin?

    https://www.eastbayinsomniac.com/wordpress

    I’m not a code person, so any help in plain English interpreting and addressing the following error is greatly appreciated:

    WordPress database error: [Table ‘eastbayinsomniac_com_-_wp.wp_terms’ doesn’t exist]
    SELECT t.*, tt.* FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id WHERE tt.taxonomy IN (‘category’) AND t.slug = ‘wordpress’ ORDER BY t.name ASC

    WordPress database error: [Table ‘eastbayinsomniac_com_-_wp.wp_terms’ doesn’t exist]
    SELECT t.*, tt.* FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id WHERE tt.taxonomy IN (‘category’) AND t.slug = ‘wordpress’ ORDER BY t.name ASC

    WordPress database error: [Table ‘eastbayinsomniac_com_-_wp.wp_term_relationships’ doesn’t exist]
    SELECT SQL_CALC_FOUND_ROWS wp_posts.* FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) LEFT JOIN wp_term_taxonomy ON (wp_term_relationships.term_taxonomy_id = wp_term_taxonomy.term_taxonomy_id) WHERE 1=1 AND wp_term_taxonomy.taxonomy = ‘category’ AND wp_term_taxonomy.term_id IN (‘0’) AND post_type = ‘post’ AND (post_status = ‘publish’) GROUP BY wp_posts.ID ORDER BY post_date DESC LIMIT 0, 5

Viewing 11 replies - 1 through 11 (of 11 total)

  • But how can I deactivate a plugin if I can’t login to my admin?

    use an ftp client. delete the files out of the plugins directory

    Thread Starter eastbayinsomniac

    (@eastbayinsomniac)

    Whooami–I just did what you suggested. Two things:

    1. All plugins except WeatherIcon were deleted. WeatherIcon contains only empty folders now (they all have read/write/execute privileges). But the plugins folder wouldn’t delete, so I renamed it plugins_old.

    2. The plugins/widgets are off the page, but the error remains.

    Any ideas/advice/translation of what the error means?

    Thanks.

    Okay, attempting to go to your admin page is redirecting me to the upgrade page, which shows the database hasn’t been upgraded yet. (Which is the source of the “table doesn’t exist” symptom.)

    However, the upgrade page is giving a 500 Internal Server Error, which seems to be a common problem. You’ll need to look in your web server’s error logs to be able to find out more about the problem. Paste a snippet at the WP pastebin for us to have a squiz at.

    Thread Starter eastbayinsomniac

    (@eastbayinsomniac)

    Hi Jeremy-

    I found this in my error log. What does this business about “referer” in the index in the mandingo/theme mean? I didn’t put a link to Insider Pages? How can I edit this or fix this without being able to get into myh admin panel?

    Thank you for looking!

    [Sun Oct 07 16:18:49 2007] [error] [client 69.105.176.10] Allowed memory size of 8388608 bytes exhausted (tried to allocate 10 bytes)
    [Sun Oct 07 16:18:49 2007] [error] [client 69.105.176.10] Premature end of script headers: php-script
    [Sun Oct 07 18:18:38 2007] [error] [client 67.180.29.142] PHP Fatal error: Call to undefined function akst_share_link() in /var/www/html/wordpress/wp-content/themes/mandigo/index.php on line 37, referer: https://www.insiderpages.com/b/9315645094
    [Sun Oct 07 18:20:22 2007] [error] [client 67.180.29.142] PHP Fatal error: Call to undefined function akst_share_link() in /var/www/html/wordpress/wp-content/themes/mandigo/index.php on line 37
    [Sun Oct 07 18:20:32 2007] [error] [client 67.180.29.142] PHP Fatal error: Call to undefined function akst_share_link() in /var/www/html/wordpress/wp-content/themes/mandigo/index.php on line 37, referer: https://www.eastbayinsomniac.com/
    [Sun Oct 07 20:19:35 2007] [error] [client 124.168.153.225] PHP Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 58368 bytes) in /var/www/html/wordpress/wp-admin/includes/template.php on line 57
    [Sun Oct 07 20:19:35 2007] [error] [client 124.168.153.225] Allowed memory size of 8388608 bytes exhausted (tried to allocate 10 bytes)
    [Sun Oct 07 20:19:35 2007] [error] [client 124.168.153.225] Premature end of script headers: php-script
    [Sun Oct 07 20:19:42 2007] [error] [client 124.168.153.225] PHP Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 58368 bytes) in /var/www/html/wordpress/wp-admin/includes/template.php on line 57
    [Sun Oct 07 20:19:42 2007] [error] [client 124.168.153.225] Allowed memory size of 8388608 bytes exhausted (tried to allocate 10 bytes)
    [Sun Oct 07 20:19:42 2007] [error] [client 124.168.153.225] Premature end of script headers: php-script

    [Sun Oct 07 16:18:49 2007] [error] [client 69.105.176.10] Allowed memory size of 8388608 bytes exhausted (tried to allocate 10 bytes)

    You’ll want to start there!

    Thread Starter eastbayinsomniac

    (@eastbayinsomniac)

    Jeremy, Handy–

    What is this business about the link FROM Insider Pages? That is a link I posted 2 years before I even had this blog. I just logged into Insider Pages and I can edit the review, but not remove the link.

    But why would that suddenly cause an error after upgrading anyway? I’d like to understand what that error means about the “referer.”

    I should have plenty memory enough to support the few pages and posts I currently have on my blog.

    My host site configuration statistics say:
    Disk Used/Allocated 25.2 MB / 1100.0 MB

    The referer [sic] link simply means what site the user came from when they triggered the error. That part of the error is harmless.

    PHP has a memory limit of 8 megabytes by default. It seems WordPress 2.3 doesn’t like the limit. You may or may not be able to fix the problem by adding the following into your .htaccess file:

    php_value memory_limit 16M

    Otherwise, e-mail your host and ask them to increase the value for you.

    Thread Starter eastbayinsomniac

    (@eastbayinsomniac)

    I wasn’t able to add that to the file. I just emailed my host. Once the php memory limit is increased, will I be able to access my admin page and perform the DB upgrade?

    I’ll post back here hopefully tomorrow as soon as I hear back. Thanks for your assistance tonight.

    I’m not 100% sure that will fix it, but if the memory problem isn’t currently the reason why it won’t work, it’ll certainly be the cause of problems in the future.

    Thread Starter eastbayinsomniac

    (@eastbayinsomniac)

    Jeremy-

    Got tired of waiting for an email response from my host; I phoned Doteasy and they did just as you suggested–increased my memory. Upon refreshing, I was instantly able to complete the upgrade and things are fine again. Thank you for your attention to this! Onward…

    I’m having the same issue. In fact, I’m seeing this issue quite a bit here in the forums but I never see where to add that memory_limit code to the .htaccess file. Does it have to be in a specific place in that file? Apparently my host can’t change this themselves.

    Many thanks!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Can’t access admin page <div id=error> after upgrading’ is closed to new replies.