Strange Characters with Spider Event Calendar – WordPress 4.01 – Graphene 1.9.4
AnonymousDecember 3, 2014 at 9:27 pm #9575
I am seeing some block-characters/images displayed on top and bottom of the page when using the Spider Event Calendar.
Also, the category links at the bottom are not displaying/activating properly.
Could this be a CSS / Template problem?
WordPress 4.01 – Graphene 1.9.4
Link to WordPress WebPage
AnonymousDecember 3, 2014 at 9:43 pm #43988
Did you have these issues before updating the graphene theme?
If not, then the following will most likely fix it. Read and install the plugin.
AnonymousDecember 3, 2014 at 10:57 pm #43989
The errors were the same before and after the update to 1.9.4.
AnonymousDecember 3, 2014 at 11:31 pm #43990
Did you install the plugin to fix your issue?
AnonymousDecember 4, 2014 at 12:12 am #43991
No… I installed the update to eliminate the version / update questions…
AnonymousDecember 4, 2014 at 12:21 am #43992
Please read the link and install the plugin that is linked within that post if you want to fix the problem.Mod
AnonymousDecember 4, 2014 at 1:30 am #43994Quote:I don’t see anything strange, except for some empty “code” elements. Can you post a screenshot of what you are seeing?
I’m pretty sure he’s missing the shortcode plugin by graphene. That’s why some shortcodes look messed up.
AnonymousDecember 4, 2014 at 2:04 am #43995
Yes, you are correct, it is the empty ` blocks at the top and bottom, and if you click on the tiny blue buttons (dots) at the bottom, the category selection is not working quite right.</p>
<p>I installed the short-code plugin you referenced, no difference.</p>
<p>I think it is probably the calendar plugin, rather than the Graphene theme. </p>
<p>The web-dorado (calendar) developers have offered to look at it… I will post on here what it turns out to be…</p>
<p>Thanks so much for your help… :)`
AnonymousDecember 4, 2014 at 12:09 pm #43996
Try to deactivate all of your plugins one by one and hard refresh (Strg+F5) your site every time to see if one of your plugins is causing the issue.
You must be logged in to reply to this topic.