unknown conflict

  • clairative

    (@clairative)


    10 years ago

    please help me.
    there is something in my wordpress (I think a jquery) that creates a conflict with almost all plugins. the problem is that when the pages are opened from the menu of the blog do not work, but if you do a refresh of the browser everything works fine.
    I do not know where and what to look for, someone has an idea?

Viewing 6 replies - 16 through 21 (of 21 total)
  • Thread Starter clairative

    (@clairative)

    Now there are two plug ins that have this problem. the problem exists even after removing the white lines.
    the theme just wants “<! DOCTYPE html>
    <html> “

    I do not understand why the plugins can be disturbed by “<html>” which is the base tag of all web pages (or not?)

    Thread Starter clairative

    (@clairative)

    what I also do not understand is why doing the refresh of the page from the browser everything works. the <html> tag is the same ….

    Moderator bcworkz

    (@bcworkz)

    Let me be sure I understand the current situation.

    Your theme and the radio player work fine with `<! DOCTYPE html>
    <html>` but you’ve identified two plugins that fail to work with the same declaration. This is on the initial page load. But if you simply refresh the same page, every thing works fine. Is this all correct?

    If so, this is starting to sound like a server configuration problem more than a WordPress problem. Who are you using as a host?

    I’m not entirely sure of all the syntax nuances, but maybe you should remove the space after the ! before DOCTYPE and provide a lang attribute for the <html> tag, like this:

    <!DOCTYPE html>
<html lang="it-IT">

    I’m assuming “it-IT” is appropriate for your site, something else may be more appropriate. I doubt any of that will make any difference, but it is more “proper” for declaring a HTML5 compliant site.

    You should try validating the site at https://validator.w3.org/#validate_by_uri+with_options . It’ll probably identify a number of issues, many are of small consequence. We’re mainly looking for serious errors.

    Thread Starter clairative

    (@clairative)

    I have tried it with any type of doctype, writing in all possible ways. plugins work removing <html> (or <html lang=”it-IT”>) … someone said to me that it might be a problem with the ajax calls, but I know little ajax, you can think of something ?

    Moderator bcworkz

    (@bcworkz)

    Hmmm, I suppose that’s possible, but I’m skeptical. What can often cause AJAX issues with WP sites is a code module not specific to WP does not implement AJAX the way WP needs it to be. It’s conceivable that the bad code could work under HTML4 transitional but not HTML5 or XHTML. The fact one element works one way and another the other way doesn’t fit the AJAX theory IMO. Besides, all the elements are written specifically for WP, they should all be implementing AJAX correctly.

    More likely, especially since you’re dealing with streaming media, is there is a mismatch with mime types. In AJAX the default is typically correct, but I’ve heard of issues with mime types before. I’m not sure the DOCTYPE would affect default mime types or not. If any AJAX request is for something besides text/html, this could be something to investigate.

    I think the critical clue is that the problem disappears when you reload the page. To me this indicates a server configuration issue. You might want to take this up with your host. Be prepared for them to say “It’s not us, it’s a WP issue.” That may not right, but that’s often what they say. Still, it wouldn’t hurt to ask.

    Thread Starter clairative

    (@clairative)

    the problem also exists in localhost. I realized that the real problem is the call to non-stop player that lets you navigate without interrupting the radio, just do not know how to work around the problem ??

Viewing 6 replies - 16 through 21 (of 21 total)
  • The topic ‘unknown conflict’ is closed to new replies.