Shashin 3.3.3 Installation

  • Hi,
    Not so much of a support request as a request to be very clear in the installation documentation.
    It has taken me ages to install 3.3.3 over the top of V3.2.6 and eventually I pinned it down to a need to deactivate and delete the Toppa Plugin Libraries item before attempting the Shashin upgrade. Without this the update gets itself into an inconsistent state whereby neither the target website nor the admin interface work any more. To recover from this it is necessary to recover both the folder/file structure and the MySQL database back to a point before you upgrade the plugin.
    Once I got to this point the installation worked fine then and the upgrade looks good.

    https://www.ads-software.com/extend/plugins/shashin/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Mike Toppa

    (@toppa)

    I’m sorry that happened. I have not run into this problem in other upgrades I’ve done so far for Shashin (but I haven’t tried upgrading from that particular older version). But the reason I removed the dependency on my Toppa Plugins Library is because of fragilities in general with dependencies between plugins. From a code perspective, the way WordPress manages plugins, subtle but significant problems can crop up with dependencies between plugins (which I’ve learned the hard way…). So you should not have problems like this in the future.

    Thread Starter MKGees

    (@mkgees)

    No problem Mike. Wasn’t really a complaint. Shashin is an excellent plug-in and I fully understand the desire to remove the dependency. Just wanted to let you know so you can note it in the upgrade guide.

    Plugin Author Mike Toppa

    (@toppa)

    Thanks for letting me know about the problem. I will add a word of caution in the readme upgrade notes.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Shashin 3.3.3 Installation’ is closed to new replies.