I switched back to version 1.7 and noticed that the colors are oké now. But still there is no navigation at the top (Search field and show – rows) in Firefox. What’s up, anyone????
Hi,
it might have to do with the two DOCTYPEs that you have defined in your source code:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
Likely this is in your theme’s header.php. I assume that the browsers each use a different one, which leads to trouble, obviously.
After fixing that, make sure that your HTML code is valid, using http://validator.w3.org
Best wishes,
Tobias
Thanks Thomas, but changing these header settings didn’t solve the problem. Although I lost 22 errors at once (thanks for pointing me out). But I found this error on this page:
http://www.mcpmusic.nl/publisher/muziek-samples/
—-
Line 193, Column 89: document type does not allow element “table” here; missing one of “object”, “applet”, “map”, “iframe”, “button”, “ins”, “del” start-tag
…”wp-table-reloaded-id-2-no-1″ class=”wp-table-reloaded wp-table-reloaded-id-2″>
✉
The mentioned element is not allowed to appear in the context in which you’ve placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you’ve forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as “<p>” or “<table>”) inside an inline element (such as ““, “<span>”, or “<font>”).
—-
I don’t know what it means, if this is causing my problems and what to do about it.
Thanks in advance Thomas
Greets John.
Hi John,
that errors seems to come from the way you have entered the Shortcode into the page. Somehow the <p> HTML tag was not closed before the table. This might have happened, if there is no line break before the Shortcode. Can you check (and eventually insert) a line break before the [table id=... /]?
Additionally, I might have found a reason for the DataTables library not working. The script is trying to load a text file which contains the translations of the used strings in Dutch, from the file
http://www.mcpmusic.nl/wp-content/plugins/wp-table-reloaded/languages/datatables/lang-nl_NL.txt
However, if I open this file in my browser, there are weird characters at the beginning of this file. Likely this is breaking the functionality. Those characters are however not in the original file in the release. Have you maybe edited this file?
Anyway, it might be worth to replace this file with the one from the release zip-file, just in case something got mangled up. It might due to the character encoding of the file, too (which should be UTF-8 or ANSI).
Regards,
Tobias
Hi Thomas,
Thanks for your effort to help me!
This is the html code for inserting the table:
—-
Klik op een kolom om deze oplopend of aflopend alfabetisch te ordenen of beperk uw selectie in het zoekvlak.
[table id=4 /]
—-
I should mention that i’m using Qtranslate plugin. So this means that there is the same code in English with the language separators <!–:nl–>dutch text here<!–:–><!–:en–>English text here<!–:–>. I just upgraded this plugin. But before I did this code was visible and I placed the Table code outside of these language separators and this didn’t make the error go away.
I looked into the lang-nl_NL.text but can’t find any weird characters in the file. I used the original from the version 1.7 that I downloaded yesterday. If I click on the link in your message above, no weird characters in Safari and Explorer but in Firefox I see these weird caracters: 
I checked the character encoding of the FTP program and the website (header and WordPress settings) and they are set to UTF-8. I have no idea at this point how to solve this.
Maybe you have a solution?
And again many thanks Tobias for your effort!
Hi,
ok, thanks for the code. Can you try to insert an empty line between the text and the Shortcode? Maybe that helps.
The qTranslate plugin could also play its role, but unfortunately I don’t know this plugin well enough to be sure it does. Can you maybe try deactivating it temporarily, so to rule out or confirm that it is the reason?
That thing with the characters is weird then. I don’t know why it is there in Firefox but not in other browsers… Could be a server configuration thing.
Can you set the encoding to “ANSI” and test again? That should remove the weird characters I believe.
Best wishes,
Tobias
Hi,
you should also update again to WP-Table Reloaded 1.8 again, as it includes a newer version of DataTables, which might not actually have that issue.
I just re-read your second post of this thread that said, that you downgraded again. I’d actually prefer to solve any issues with the latest version.
Regards,
Tobias
Hallo Tobias,
I already switched off the Qtranslate plugin and several others but without any changes.
I just upgraded to 1.8 again and things have turned worse again in Firefox. Table colors are gone also.
where do i set the encoding to “ANSI”? In the server settings from the hosting is no ANSI available. If set to standard ISO ISO-8859-1 or UTF-8 makes no difference.
I did set it manualy to ANSI but I don’t know if this is correct and it didn’t change anything.
Thanks again!
Hi,
the table colors going away is very likely related to the sorting not working. The script first performs some “cleanups” on the HTML of the table, before restoring those settings (e.g. the code for alternating row colors). But, before it can do this restoring, it bails out, likely due to that problem of loading the translation strings.
So, we should examine this encoding thing closer: With changing to ANSI, I do not mean to change any server settings, so you should restore those to the values they had before. Instead, take the lang-nl_NL.txt file, download it via FTP, open it in Notepad, “save as” with “ANSI” encoding (can be selected at the bottom) and upload that again.
Tobias
Yes! That did the trick. Although I couldn’t save the file as ANSI (I’m on Mac OS with texteditor) I used ASCI 2 instead and now things work as they should!
Super fantastic Tobias, You really rock!
Hi,
great to hear that this worked 🙂
Just to remind you: You might have to redo this step after each update in the future. However, I will of course try to find a permanent solution.
Best wishes,
Tobias
