Bug with Post Data field

  • Resolved lalbertini

    (@lalbertini)


    5 years, 6 months ago

    Hello,

    I deployed Forminator, and I think it’s really great.
    I’m just encountering a bug with the “post data” field.

    The problem:
    When inserting a group of “post data” fields and activating the “Content” field, the display of the latter is correct only on chrome.
    On other browsers, the “visual” and “text” tabs, as well as their associated edit buttons, dont display correctly (which creates a very naughty look on SAFARI mobile). This seems to be a JS problem.
    Moreover on all tested browsers, the “full screen” button does not work (but it is already less annoying).

    Another slightly worrying point ( because it makes Google furious 🙂 ), the addition of a “post data” field on the page, generates an h1 :
    <h1 id=”link-modal-title”>Insert/modify a link</h1>

    Did you encounter the same problem(s) when using this field?

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Predrag – WPMU DEV Support

    (@wpmudev-support1)

    5 years, 6 months ago

    Hi @lalbertini,

    I did some tests with Post Data form on my end (only on Win10 so far) and I was unable to replicate issues that you mentioned in Chrome, Opera, Edge or Firefox.

    However, when I check your site in those browsers I do see some issues with the look of the Text/Visual switcher and that the fullscreen button doesn’t work.

    It seems that there’s something specific on your site that is causing this issue, so could you perform a conflict test by disabling all your other plugins and switching to default WP theme to see if it works fine after that?
    If it does, enable them back one by one until the issues are back and that should tell us where the issue is coming from so we can debug it further.

    I suggest doing this test on a staging site or if you don’t have one make sure to have a full backup of the site before doing the test on live installation.

    Another slightly worrying point ( because it makes Google furious 🙂 ), the addition of a “post data” field on the page, generates an h1 :
    <h1 id=”link-modal-title”>Insert/modify a link</h1>

    Forminator uses default WP post editor (Classic one) and H1 is the default part of it, and while multiple H1 on page was frown upon by Google in the past, their algorithms have changed a lot over the years and don’t see issues with that anymore.
    You can also check about that in this video here:

    Cheers,
    Predrag

    Thread Starter lalbertini

    (@lalbertini)

    5 years, 6 months ago

    Hello,

    Thank you very much for your complete and very detailed answer.
    I was able to proceed to a debug on my staging server.

    The problem comes from the deletion of the css file related to the dashicons

    function wpdocs_dequeue_dashicon() {
    if (current_user_can( ‘update_core’ )) {
    return;
    }
    wp_deregister_style(‘dashicons’);
    }
    add_action( ‘wp_enqueue_scripts’, ‘wpdocs_dequeue_dashicon’ );

    When I remove this “optimization”, the field has the normal behavior on all browsers.
    I don’t understand why this doesn’t affect Chrome 🙂

    Thanks also for the precisions on the use of several H1 tags.
    I didn’t think Google had become more “relaxed” on the subject 😀

    Nice day to you,

    Laurent

    • This reply was modified 5 years, 6 months ago by lalbertini.
Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Bug with Post Data field’ is closed to new replies.