• I was going along happily editing my content when BOOM, everything disappeared to be replaced with the following:

    Warning: array_key_exists(): The first argument should be either a string or an integer in [site]/wp-content/plugins/tailor/includes/class-custom-css.php on line 195

    Upon further investigation it appears that all the tailor serialized metadata id’s and parent id’s have been set to INF, e.g.:

    a:5:{s:2:"id";d:INF;s:3:"tag";s:12:"tailor_image";s:4:"atts";
    a:5{s:10:"image_size";s:4:"full";s:17:"shadow_horizontal";s:1:"0";
    s:15:"shadow_vertical";s:1:"2";s:11:"shadow_blur";s:1:"6";s:13:"shadow_spread";
    s:1:"0";}s:6:"parent";d:INF;s:5:"order";i:0;}i:3;

    This is a huge issue, as I’ve spent hours building the page for a misconfiguation on save overwrote all IDs with infinity….

    Do you have any suggestion on how to remedy this situation besides starting from scratch and rebuilding the page?

    Thanks!

    • This topic was modified 7 years, 12 months ago by gnowland. Reason: formatting
Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter gnowland

    (@gnowland)

    Thank God for post revisions! I was able to restore the post to a previous revision, which contained good ID/Parent data. Needless to say I’m a bit shook up that everything went *POOF* so abruptly, so if there’s anything I can do to help you patch this particularly nasty bug let me know. I have database backups and such.

    Cheers,
    Gifford

    Plugin Author Andrew Worsfold

    (@andrewworsfold)

    Hi Gifford,

    Thanks for raising this!

    I have not had any other reports of this, nor have I seen this myself during testing, however will treat this will the utmost urgency. I’ll try to reproduce it on my end and to help in that effort I am wondering:

    1. Are you/were you using any other plugins?
    2. Which theme are you using?
    3. Is there anything else notable about your environment?
    4. Have you extended Tailor in any way?
    5. Can you remember what changes you were making before encountering this error?

    Database backups etc may be useful once we get a better handle of what happened.

    Cheers,
    Andrew.

    Thread Starter gnowland

    (@gnowland)

    Hi Andrew, thanks for getting back to me, I’ll do my best to try and help recreate the issue!

    1./2. I’m working on a custom theme built on Sage (https://roots.io/sage/), with a “custom functionality plugin” (https://github.com/gnowland/wp-jet-fuel) among others:

    
    wp plugin list
    +-----------------------------+--------+--------+---------+
    | name                        | status | update | version |
    +-----------------------------+--------+--------+---------+
    | ewww-image-optimizer        | active | none   | 3.1.3   |
    | intuitive-custom-post-order | active | none   | 3.0.7   |
    | ninja-forms                 | active | none   | 3.0.16  |
    | ninja-forms-conditionals    | active | none   | 3.0.8   |
    | seedprod-coming-soon-pro-5  | active | none   | 5.2.8   |
    | soil                        | active | none   | 3.7.1   |
    | tailor                      | active | none   | 1.7.7   |
    | tailor-advanced             | active | none   | 1.0.1   |
    | wp-jet-fuel                 | active | none   | 0.0.1   |
    | wp-mail-smtp                | active | none   | 0.9.5   |
    +-----------------------------+--------+--------+---------+
    

    4. I Haven’t extended Tailor
    5. While the tailor edit page was open I added a new shortcode to the functionality plugin (wp-jet-fuel) and was adding the default “Text Widget” to my footer widget area.

    Am I right in understanding that the Tailor plugin uses the WP REST API to perform save actions? Before realizing that the wp_post table contained backups of post metadata and doing the post restore I briefly started stepping through the Tailor code :). Possibly something with the Widget save action clashed with a Tailor page save?

    I hope this information is helpful and please let me know if you need clarification on any of the above or otherwise.

    Cheers,
    Gifford

    • This reply was modified 7 years, 11 months ago by gnowland.
    Plugin Author Andrew Worsfold

    (@andrewworsfold)

    Hi Gifford,

    Tailor doesn’t yet use the REST API, however this is an upcoming change given that everything that’s needed is now in core ??

    At present, a save action is triggered using AJAX; this serves to do a number of things including save layout meta information (the element “models”). What you describe above shouldn’t affect any of this, however, so I am very curious to know what the cause is.

    I’ve installed and activated the wp-jet-fuel plugin and have so far been unable to reproduce the problem. When you say you “added a shortcode to the functionality plugin”, what do you mean?

    I will keep testing but in the meantime please let me know if you have any luck reproducing it on your end.

    Cheers,
    Andrew.

    Thread Starter gnowland

    (@gnowland)

    By “Added a shortcode to the functionality plugin” I literally mean:

    https://github.com/gnowland/wp-jet-fuel/commit/cce4dcaa231fce52e75f805b37a5104fd186fdbe

    ??

    I wish I had more info to provide you…

    Thanks again for your attention and expeditious response! I gotta say, this is a fabulous page builder, thank you for open sourcing it. Your code is top-notch!

    Cheers,
    Gifford

    • This reply was modified 7 years, 11 months ago by gnowland.
    • This reply was modified 7 years, 11 months ago by gnowland.
    Plugin Author Andrew Worsfold

    (@andrewworsfold)

    Ah, I see ??

    Unfortunately I still haven’t managed to reproduce what you saw, but I will keep trying. Please do let me know if you have any luck doing so on your end.

    Thanks so much for your kind words about the plugin, I really appreciate it ??

    Cheers,
    Andrew.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘All tailored content is broken! $sanitized_model[‘id’] returning float(INF)’ is closed to new replies.