• Resolved Joe Hana

    (@joehana)


    Hi,

    thanks for the latest update. In the meantime I found that the plugin generates additional markup in the frontend

    <div id="examplePopup1" style="display:none;"><div style="float:left;padding:20px 20px 20px 20px;"><h4>Enter your email Address</h4><input type="text" style="margin-top:10px" name="useremailID" id="useremailID"><input type="hidden" id="emailpostID"><input id="guest_email" style="margin-top:10px" class="button-primary" type="submit" name="email_submit" value="submit"></div></div>

    I’m not quite sure why it does that but I’m certain this shouldn’t happen.

    Thanks for looking into it

    https://wordpress.org/plugins/wp-advanced-pdf/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Joe Hana

    (@joehana)

    Further it seems like right below this additional markup, it prints parts of the head incl. meta tags and link elements (<link rel=”” href=””>)

    Plugin Author cedcommerce

    (@cedcommerce)

    Hello Joe Hana,

    We didn’t found any markup when “Frontend” check-box is not selected from settings in admin panel, let us know where you have find this, we will definitely do the needful.

    Thank you

    Thread Starter Joe Hana

    (@joehana)

    Well, it’s pretty funny that you claim that you didn’t found that markup, since it is clearly available within the source code of the plugin.

    See wp-advanced-pdf.php on line 262 the function ptp_hook_div_for_guest? And it gets hooked on line 61 to the WP_HEAD. Why? Why does markup get hooked in the head? That doesn’t make any sense. And as it seems – there is no check included for the “frontend” or for a specific kind of users. This gets straight added to WP_HEAD in any case.

    Plugin Author cedcommerce

    (@cedcommerce)

    Hello Joe,

    We didn’t get your point in previous message. Now we got what you wanna explain and we will assure you that we will fix this in our next version.

    Again thanks for such notification.

    Thanks
    CedCommerce

    Thread Starter Joe Hana

    (@joehana)

    Hello,

    sorry if I sounded to harsh. It was quite early in the morning and don’t know…somehow I wasn’t able to clearly explain the issue. Sorry for that.

    Looking forward to the fix.

    Plugin Author cedcommerce

    (@cedcommerce)

    Hello Joe Hana,

    We had updated our plugin, so please let us know about the issue you mentioned is fixed if not then please inform us.

    We always welcome these kinds of reports about our plugin because on fixing them we got chance to make our plugin best.

    Thanks again
    CedCommerce

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘#examplePopup1 in frontend source’ is closed to new replies.