WordPress.org

Forums

WP-Table Reloaded
[resolved] Not fully compatible with WP3.5: Changes don't save (4 posts)

  1. Nonstopdrivel
    Member
    Posted 2 years ago #

    We have been using WP-Table Reloaded for months without a hitch. This morning we upgraded to WP 3.5 and now we are starting to notice some erratic behavior in the plugin.

    For example, we routinely uncheck the "Every second row has an alternating background color" and "The first row of your table is the table head (HTML tags <thead> and <th>)" boxes so that we can customize the first table row with CSS. Now since the upgrade, these boxes randomly recheck themselves, resulting in the tables looking differently than we want.

    The other issue is that edits made within the Edit Table page are randomly being reverted to the original version of the table as created before the upgrade. I have had to re-edit a table we published this afternoon several times. At this point it's not worth dealing with, so we will wait until the bug is resolved before updating our tables again.

    Thanks for a great plugin. We hope that it can be brought into full compatibility with WP 3.5 as soon as possible.

    http://wordpress.org/extend/plugins/wp-table-reloaded/

  2. TobiasBg
    Member
    Plugin Author

    Posted 2 years ago #

    Hi,

    thanks a lot for your post, and sorry for the trouble!

    To be honest, I don't think that this is related to WordPress 3.5. I've been following WP core development closely, and there were no changes that would directly affect WP-Table Reloaded and its saving mechanism. Also, I can't reproduce this on any of my just updated test sites.

    Instead, I assume that you are affected by one of two possible server issues, that has been happening more and more in the past. One of them is the change of a default value in the the configuration of PHP 5.3, and the other is the usage of the Suhosin security extension on the server. Both of these can lead to saving issues in large tables, which show very similar symptoms to what you describe.

    Fortunately, there's rescue in sight: During the last months, I have been working on the designated and official successor of WP-Table Reloaded, called TablePress. TablePress is a completely rewritten version of WP-Table Reloaded, and due to some nice changes in the internal data structure and the saving mechanism, it is not prone to the aforementioned issues. Therefore, I suggest that you migrate from WP-Table Reloaded to TablePress now. You can get the plugin at http://wordpress.org/extend/plugins/tablepress/ and can get more information on how to switch at http://tablepress.org/migration-from-wp-table-reloaded/

    Best wishes,
    Tobias

  3. Nonstopdrivel
    Member
    Posted 2 years ago #

    Naja, du bist der Pluginentwickler, du würdest besser als ich wissen, was dieses Problem aufwerfen würde. Ich finde es einfach komisch, dass wir dieses Plugin so lange ohne Probleme benutzt hatten, und diese Bugs heute Nachmittage plötzlich aufgetaucht haben, sobald, dass wir WordPress aufgerüstet haben.

    Jedenfalls probieren wir TablePress, wie du vorschlägst. Ist TablePress kompatibel mit WP-Table Reloaded, oder müssen wir unsere bereits bestehende Tabellen wieder anlegen?

    Danke sehr für die Hilfe!

    P.S. Ich bin doof. Ich habe gerade den Link gesehen. Bitte an meine Frage vorbeigehen.

  4. TobiasBg
    Member
    Plugin Author

    Posted 2 years ago #

    Hi,

    very likely the problem has existed for some longer time, and you just didn't spot it right away.

    But, no matter where it came from, switching to TablePress should fix your problems :-) And yes, as you have seen in the link, tables can be migrated and don't have to be re-done.

    Best wishes,
    Tobias

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • WP-Table Reloaded
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic

Tags

No tags yet.