Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor fireproofsocks

    (@fireproofsocks)

    I haven’t heard of that behavior. Are you running any install scripts? Sometimes install events can flush the wp_options (where the CCTM definitions are stored).

    Thread Starter knsheely

    (@knsheely)

    I’m not running any install scripts. The rest of the wp_options table remains intact. It is only the cctm_data row that is reverted.

    Plugin Contributor fireproofsocks

    (@fireproofsocks)

    next guess would be that there’s a diff between the version of CCTM installed and the version that’s pegged in the db. B/c WP doesn’t have an event for “onPluginUpdate”, I had to roll my own: the CCTM compares its php class variable for a version number with a version number stored in the db. When you first download an update (either manually or via wp), the version number in the file will be greater than the one in the db, so update code can run. If that got out of sync somehow (eg by copying data from another install), it could be triggering the update process when it shouldn’t be.

    Thread Starter knsheely

    (@knsheely)

    It appears that the cctm_version value is 0.9.7.11-pl in the database. The version on the plugins page also says version 0.9.7.11. Does the pl mean anything?

    It is the same on the live site.

    btw, thanks for your help.

    Plugin Contributor fireproofsocks

    (@fireproofsocks)

    pl is a common suffix used for versioning to indicate a public release (pl = public). See https://php.net/manual/en/function.version-compare.php

    Hmm… I’m not sure what else to eyeball… wish WP had logging features… is this only happening in your dev environment? Because I’ve not seen/heard of this issue before, I suspect it may have to do with the environment, which makes it hard to troubleshoot…

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Site Definitions Revert on Development’ is closed to new replies.