Install error to 1.7 « WassUp Forums

WassUp Forums » WassUp Support

Install error to 1.7

(12 posts) (2 voices)

Started 1 year ago by PBCliberal
Latest reply from PBCliberal

Tags:

PBCliberal
Member

I upgraded to wassup 1.7 using auto-upgrade, and the new install fails activation with:

Fatal error: Cannot redeclare wassup_install() (previously declared in [accurate path]wp-content\plugins\wassup\wassup.php:55) in [accurate path]wp-content\plugins\wassup\wassup.php on line 145

[I removed the full pathname for security reasons, but it's right]

I then uninstalled and removed the old directory (which included a version number), and reinstalled automatically by uploading zip, which fails the same way.

I'm not very fluent in php, but I am a programmer and I'll hack anything. Ideas?

(I tried to open a ticket but my submission was rejected as spam)

Posted 1 year ago #
helene
Moderator

PBCLiberal,

We have only seen your type of error with non-standard WordPress configurations. Can you give us more detail about what versions of Wordpress, PHP, and MySQL you are using and whether you have changed or renamed "/wp-admin/" or other key directories and if your blog is on a Linux or Windows server.

-Helene D.
http://www.techfromhel.com

Posted 1 year ago #
PBCliberal
Member

WP 2.7.1
MYSQL 5.0.45-community-nt
PHP 5.2.3 (isapi)
Windows 2003 Server Web Edition SP2

No directories have been renamed, and everything works fine running Wassup 1.6.4, I've installed and uninstalled it and 1.7 several times in trying to get a clue. The relevant SQL tables look to be fine, as well, just missing any data from when 1.6.4 isn't running.

The blog in question is the one linked to my username here. Thanks. Let me know if you'd like me to try any test code. My blog isn't exactly setting the world on fire, so if we accidentally trashed it for a couple of days it would be no great disaster.

Posted 1 year ago #
helene
Moderator

Thanks for the info. That helps alot.

You might want to try manually deactivating WassUp 1.6.4 in Wordpress Plugins page. Then, after you get the "plugin deactivated" message, reselect the Plugins page (don't reload the page, click on Plugins button again). Look at your plugins list and make sure Wassup 1.6.4 is no longer activated and that you don't have the Wassup menu in your admin sidebar. Then, upgrade to Wassup 1.7 and manually activate it when the upgrade is done. Let me know if this makes any difference.

Also, I have more questions for you: Was the initial upgrade from WassUp 1.6.4 to Wassup 1.7 the first time you ever did an upgrade of WassUp? Or did you have an early version of Wassup that pre-dated Wassup 1.6.4? If you did, what was that version and did you upgrade it via Wordpress' automatic upgrade?

Posted 1 year ago #
PBCliberal
Member

Got identical results. The only thing different about our installation is that the whole wwwroot hive is not on C: where server would initially install it, but on a redundant raid which we call Z:.

But the relative pathing from that point forward is absolutely default standard garden-variety ordinary. I'm not sure your php code would even have a way to detect this, and it has never otherwise caused us a problem. This is not something we can change (since there are lots of sites on this webserver, including a forum which shares MySQL).

Posted 1 year ago #
PBCliberal
Member

And one more thing (hit "send post" too soon), I've upgraded faithfully and automatically two or three times always staying current. I'm swamped with other code (in languages I actually understand), but if I have a moment, I'll hack around a bit.

Posted 1 year ago #
helene
Moderator

PBCliberal,

If you have a busy site and/or a software caching system in place, this could affect WassUp "uninstall". Queued records has to finish writing to the database and software changes related to "deactivation" has to propagate the cache before WassUp "uninstall" can complete. If this is the case for your site, try manually deactivating Wassup and wait a couple extra minutes afterwards for the "uninstall" to finish, then do the upgrade.

If that is not the case, then Wordpress plugin installer or another plugin could be interfering with WassUp's uninstall. Try deactivating ALL plugins, upgrade to Wassup 1.7.1, then reactivate plugins.

Finally, if that does not work and you have not done this before, try a manual upgrade instead of automatic: deactivate and delete Wassup 1.6.4 completely from the plugins directory, then copy Wassup 1.7.1 to /wp-content/plugins/ and activate.

Good luck.

Posted 1 year ago #
PBCliberal
Member

No, that didn't work either. I am next going to try removing every trace (except the database) restarting the server and trying an uninstall (I'll wait for an overnight to do that) and if that doesn't work, I'll eliminate all the tables associated with the plugin and try a fresh install. (I know I'll lose the history, but I'll get the space back!)

Posted 1 year ago #
helene
Moderator

PBCliberal,

I was finally able to reproduce your activation error on my server, but not in Wordpress 2.7.1 - in Wordpress 2.8 beta1.

However, despite the "fatal" error message saying that it could not be activated, WassUp did in fact activate. In case the same thing is happening in your situation, try activating Wassup 1.7.1 again and, after you get the activation error message, click on "Plugins" button again or check the sidebar menus for Wassup to verify that Wassup 1.7.1 did activate.

I should have a fix soon, unless the cause is a bug in the new Wordpress itself.

Posted 1 year ago #
PBCliberal
Member

Yes, I think you are duplicating my situation, because in fact when I attempt activation and get the fail message I do get the sidebar and everything seems to work fine, except that I get no inserts into the database from visits, and before long I get a message that there aren't enough records to display when the viewport is set to 24 hours.

I've upgraded to 2.7.1 and will let it cook that way for a while to make sure that condition still exists. Let me know if you want me to try anything based on this new information.

Posted 1 year ago #
PBCliberal
Member

Going into MySQL and deleting the wp-wassup and wp_wassup-tmp tables completely allowed 1.71 to install without a problem. Of course, I lost my history, and I don't know yet if everyting is working but it wrote one record so far to wp_wassup_tmp.

We'll see, but if you made any database changes as a part of the upgrade, perhaps that's where it failed.

Posted 1 year ago #
PBCliberal
Member

I now discover no new records go into the wp_wassup table. I have uninstalled and removed the tables in MySQL in the hopes a later version will solve this problem.

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.