rodeboy
Forum Replies Created
-
Thanks to both of you. The CSS has always been, and continues to be in my themes Custom CSS options. I tried moving it to the Gallery CSS but with no luck. Like jlevant there is what appears to be new white borders around the thumbnails and, I too cannot tell what elements are involved.
If we could be told what the new element is I think we could get rid easily. Further advice would be appreciated.
Thanks again
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Clicking Next Month ErrorIf you go through the All in One Calendar page on WordPress.org and view the Support tab the Subject is “Events – SyntaxError” at https://wordpress.org/support/topic/events-syntaxerror?replies=19
Good luck
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Clicking Next Month ErrorIt’s the same issue. Check the ‘Syntax Error’ chain of correspondence where both of us have now resolved the problem. Follow the suggestions made there. Hope that helps.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Events – SyntaxErrorThank you for the update Pavel. I found the same issue reported here at https://time.ly/forums/topic/syntaxerror-unexpected-token/ and working my way through this I did all of the following;
1. Go to Events->Calendar Themes and change the calendar theme to Vortex. If it’s already Vortex, change it to a different theme (eg: Plana) then back to Vortex.
2. Go to Events->Theme Options and hit the “Save Options” button (without changing anything).
3. Go to Settings->Permalinks (in the WP settings) and hit “Save Changes” (without changing anything).
4. Within ithemes security plugin uncheck for an option about removing “suspicious query strings”At present I can (somewhat nervously!) report that it seems to be okay and not throwing out this error anymore. I don’t know which of these solved the issue, or if indeed it is solved on a long term basis. I provide the feedback as it may help your investigations Pavel.
I will check my sites tomorrow.
By the way, I love the plugin … when it is working well! However its temperamental nature with updates (both itself and with wordpress) does test my patience at times!
Chris
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Clicking Next Month ErrorThis problem raised as a separate issue on the support page with heading ‘Syntax Error’, so suggest you cross refer. Unfortunately no solution provided there either.
Surely a major issue like this needs sorting urgently regardless of whether someone has priority support or not.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Events – SyntaxErrorOkay, thanks for the clarification. Can Steve and myself now have a solution to our problem please?
I use the plugin on several of my sites and they all have the same issue which does not look good for my clients, or on me.
Can you give this some priority now please?
Thanks, Chris
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Events – SyntaxErrorHi Ben, I take it that your response applies to me too!! I have tried your suggestions 1 – 4 but that does not change things. I use W3 Total Cache.
As it loads correctly on refresh, it would appear to me to be a cache issue.
Look forward to a prompt solution. I actually thought that version 2.3.8 was addressing this in view of Changelog info, but clearly not. Incidentally 2.3.8 was meant to improve loading speed by enabling Front-end Rendering by default, but box is not checked by default.
Thanks, Chris
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Events – SyntaxErrorAlso happening on another site of mine at http://www.deano.org.uk/gigs-calendar/ so clearly there’s an issue with the plugin and WP compatibility in my opinion.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Events – SyntaxErrorSimilar problem. I now get the following when clicking to the next month. But then if I refresh the page it works fine. Something isn’t quite right.
“Something went wrong while fetching events.
The request status is: 200
The error thrown was: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data”Thoughts anyone? Site is at http://www.leevasey.co.uk/gigs-calendar/
Many thanks,
ChrisForum: Plugins
In reply to: [Timely All-in-One Events Calendar] Cannot Edit event after upgrade to v2.0.7For anyone affected by this issue version 2.0.8 has just been released specifically to address them. I have updated to this without issues and all is working fine.
Forum: Fixing WordPress
In reply to: Running v4.0-alpha and I don't know why!If people still have this issue just to let you know that I followed the instructions given in the link proved by Lee Willis and it worked perfectly.
I did take a full backup, but this was not needed.
Forum: Fixing WordPress
In reply to: Running v4.0-alpha and I don't know why!Glad I’m not alone! Now what do we do?!!
Seems like it’s an issue with the development of v4.0 in en-GB
Forum: Fixing WordPress
In reply to: Auto update removed _GB versionThat’s great mattyrob. I have since found one or two articles providing guidance on this, but this as the title says is the definitive guide.
Any ideas on getting my GB version back?
Chris
On my site AboutThemShoes(dot)co(dot)uk I am having to keep rolling back to v1.9.13 as the gallery images have a nice fine shadow to them, but on upgrading to all the v2 the white background re-appears.
Currently I have CSS code
.ngg-gallery-thumbnail img {
background-color: #141414;
}
changing the background of the thumbnails to the same as the main background, but this coding has no effect in v2.Using Graphene theme
I have had the same issue as Sandstorm_gaf. There is a conflict with CKEditor plugin that needs adding to your list.
Like many I like the NextGen plugin, but I find it amazing that so many issues are coming to light following the launch of version 2.0, suggesting to me that it wasn’t tested well enough before launch.
Even more amazing is that the plugin is still available as V2.0. May I respectfully suggest that the 2.0 version is pulled, reverting back V1.9.13 to avoid further problems for the millions of users of this plugin as they come to upgrade. It can be re-launched once corrected and fully tested.