Although Firefox displays a clean page, IE8 shows errors on the page when OrgSer 2.1.1 is activated. If I deactivate it, the error on page clears. It does it on Darren's page as well. I don't usually use IE so it is configured as "out-of-the-box" - just the way most of our users will have it configured.
I am using self-hosted WP 2.8.4 and the particular theme does not seem to have any effect. I have tried it on 3 o 4 different themes and all act the same. Neither does it appear to be a conflict with another plug-in.
OrgSeries is still working on my http://chiefshepherd.com site but I decided to disable it on my http://raywaldo (technology) site. It just doesn't refect good technology <grin> to have errors on your own page. As I said, my copy of IE8 shows the "error on page" for your main site also.
Any idea what is causing it?
Ray
IE8 shows errors on page
(11 posts) (5 voices)- Started 4 months ago by ray
- Latest reply from Darren
- This topic is
resolved
-
Posted 4 months ago #
-
I am seeing this too: "error on page" in IE8 with Org Series activated, goes away when deactivated.
Posted 4 months ago # -
I'll check into this as soon as I get a chance. I suspect it is has something to do with javascript I have with the "series" widget...is that being used on either of your blogs?
Posted 4 months ago # -
No, I'm using a text widget to link to series on my blog, so I don't think that could be it.
Posted 4 months ago # -
Hey Darren: I use the "series widget" on both of my sites. In clarity, I do NOT find anything that is not working properly. The ONLY issue is the error message in IE (actually, I think it is in all versions of IE.) If we could just convince everyone to start using a GOOD browser (say, FireFox), then all would be well <grin>.
Posted 4 months ago # -
I've confirmed this error and it is related to some .js code Organize Series inserts for using the dropdown selector for series archives. The .js code is loaded even when the widget is not active. It's also bad form to have .js scripts right in the body of the html. That is more than likely why the error is being reported by IE8. The good news is that this won't affect the functionality of your site in anyway. It does however break standards.
I've bumped this to the top of the fix list for the next release.
Posted 4 months ago # -
I've fixed this locally by checking the return value from any calls to
document.getElementById("series");So, for example:
var seriesdropdown = document.getElementById("series"); function onSeriesChange() { // ... } seriesdropdown.onchange = onSeriesChange;becomes:
var seriesdropdown = document.getElementById("series"); if (seriesdropdown) { function onSeriesChange() { // ... } seriesdropdown.onchange = onSeriesChange; }Also, I'd recommend a less generic id that "series" (like "organize_series_seriesdropdown") to avoid potential conflicts.
Posted 3 months ago # -
Yeah that's pretty much fix I've implemented in the next version slated for release (I should just get it out already...I'm just working on one more thing). Thanks for posting here though for people who want to get it taken care of right away.
As for your suggestion on the id change... good point! I think I'll do that - you're right series is too generic.
Posted 3 months ago # -
The new release is out with the fixes (I also did the id change as suggested)
Posted 3 months ago #
Reply
You must log in to post.