jdaniel

jdaniel

@jdaniel

Viewing 4 replies - 1 through 4 (of 4 total)
Author
Replies
  • in reply to: Problem with The Grid plugin #2936

    Thank you!

  • in reply to: Problem with The Grid plugin #2934

    The answer I got is this:

    [blockquote]Hello,

    The Grid use native WordPress title and name fields. We also use native metadata fields to store all options. Nothing is undefined when a grid is saved. Isset and empty are two different things. A filed can be empty but definied in WordPress. The result is not the same.

    In WordPress when you save a post/page with metadata, even if the field is empty for a metadata then it’s set and definied to empty. WordPress do not ignore metadata since it’s a part of the core functionnality: https://codex.wordpress.org/Metadata_API

    Themeone[/blockquote]

    Does this help? Any further questions?

  • in reply to: Problem with The Grid plugin #2932

    Hello Milan,

    All I can say is:

    1. If I run Smart Cleanup Tools and let “postmeta record” be emptied the grids disappear from the backend/admin interface. They are still there (and in the frontend), but since I can’t edit them in the backend anymore it’s not an option.

    2. If I rund Smart Cleanup Tools and exclude “postmeta record” the grids don’t disappear from the backend/admin interface.

    So you see there definitely is a correlation between these two. I tried many other things to make sure it’s related to that and I can confirm that this is the case.

  • in reply to: Problem with The Grid plugin #2929

    I also asked Themeone about it. They answered:

    [blockquote]Hello,

    I think this plugin think that The Grids are empty because we removed post title or some other fieldd (which is a native functionnality of WordPress). So this plugin remove everything and which seems empty but there is data inside each grid. Grids are post type, so this plugin remove all grids but grids are not empty at all.

    Themeone[/blockquote]

    [hr]

    [blockquote]Hello,

    I don’t know. it’s an issue related to your plugin. You must contact the plugin author to solve this issue.
    Thank you for your understanding.

    Themeone[/blockquote]

Viewing 4 replies - 1 through 4 (of 4 total)