cefiar
Forum Replies Created
-
You might want to download the latest translations from Time.ly GlotPress: https://translate.time.ly/projects/timely/all-in-one-event-calendar/212
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] 500 Internal Server Error" on ALL PAGES!As per my other reply, this seems like a memory limitation.
500 errors usually indicate a memory limitation. Use a plugin like WP-Memory-Usage to confirm your PHP memory limits. See https://wordpress.org/plugins/wp-memory-usage/
I recommend AT LEAST 16MB more than you use on average, with 32M being better. Most installs work fine with a limit of 128M, which is now the default for 5.2.1+ (some hosts reduce it to save on memory).
Note: I advise using a plugin to check, as this will see any limits imposed on WordPress at all levels (including in wp-config.php), not just what your host says your limit is.
BTW:
get_the_title()andthe_title()can return HTML. If your plugin expects no HTML in the title of a post/page, it needs to be updated to fix it, so what you’ve done is pretty much the right way to go about it.Note that if something was using
the_title()they could use functionthe_title_attribute()instead.To be specific, the WP-Typography plugin also puts HTML in titles, so the same bugs that you’re seeing with the sharing plugin are going to happen if you were using the WP-Typography plugin instead.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Doesn't look right on mobileGoogle calendar supports HTML in event details on the web version of Google calendar, but not on the mobile version of Google calendar.
It’s an annoyance that bites a lot of people.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Are you sure you want to do this?Can you confirm which version of Ai1ec you’re using? I think 2.1.1 had a problem with cloning events.
FWIW: I get that out of WordPress on any sort of admin function (rather than navigation) if I’ve not used the admin page for a while:
eg: Load up Dashboard->Plugins. Go away from the browser tab for 4+ hrs, leaving the browser open (ie: using other tabs, doing other stuff on my computer, having a life, etc). When I come back if I then click on “Disable” for any plugin, I’ll get that message.
Note: I’m not trying to say you don’t have a problem, but it’s a WP error message and not specifically an Ai1ec one, which might make it harder to track down the issue.
You might try this fix which resolves another issue. It might be a different manifestation of the same problem.
https://time.ly/forums/topic/wrong-information-in-event-detail/#post-135427
Note: A fix for this should end up in 2.1.3 with any luck. I’ve poked my contact in Time.ly about it.
Forum: Plugins
In reply to: [Simple Share Buttons Adder] Title plugin conflictFWIW: Looking briefly through the code it’s using
get_the_title()in two places, both of which probably should be replaced withthe_title_attribute()assuming that the plugin runs in the loop.If it doesn’t run in the loop, then you should really consider stripping HTML tags from get_the_title() using something like strip_tags() or the like.
They’re in the file simple-share-buttons-adder.php and appear on lines 701 and 707.
Hope this helps.
BTW: Where this breaks most often is when the title gets used as a html tag attribute and it itself contains an attribute. As soon as the second quote is hit, the html becomes invalid.
The version you mention before 1.10.11 is.. well.. really old or not even an ai1ec version. It’s definitely more than 2 years old or more.
I’d suggest you post about this issue on the support forums at Time.ly – https://time.ly/forums/
Note: After you post a public post there, you can reply to your own post with a Private reply that contains the detail of the error (eg: text pasted or a readable screenshot) that might allow one of the moderators or the Time.ly employees to resolve the issue.
There is an issue that affects some people saving settings: See https://time.ly/forums/topic/settings-errors-on-latest-update-2-1-1/page/2/#post-135175
Note: This issue is due to either the MySQL database or the PHP Database layer not supporting Unicode (UTF8) in queries. You may want to talk to your host as more and more code will be using unicode in the future.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Downgrade 1.10.11 / 2.0.5 to 1.10.9Fix for the Save Settings bug in 2.1.1: https://time.ly/forums/topic/settings-errors-on-latest-update-2-1-1/page/2/#post-135175
Performing a manual upgrade/downgrade: http://time.ly/document/troubleshooting/perform-manual-upgrade/
All user guides are now at: http://time.ly/support/user-guide/
Note: support.time.ly was shut down. The content worked for old versions only and many people were still referring to it thinking the processes were valid for 2.x series products.
Also: If you paid a license for the plugin, you really should use the forums at https://time.ly/forums/ as that’s what they’re there for.
To fix settings, see this post on the Time.ly forum:
https://time.ly/forums/topic/settings-errors-on-latest-update-2-1-1/page/2/#post-135175
Note: This is the MySQL database or PHP database layer on your host not handling Unicode (UTF8) characters.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Individual event not loading500 errors with Ai1ec tend to be WP/Ai1ec hitting PHP memory limits.
Suggest you install a plugin like WP-Memory-Usage to see what WP and plugins think the memory limits are. This way you get definitive answers on what WP/Plugins think, rather than just trusting settings in config files.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] Width Display IssueYou need to widen the central content area for your theme in CSS.
I had a quick look, but couldn’t identify which classes needed to be set, even if I was to hide the sidebar.
Forum: Plugins
In reply to: [Timely All-in-One Events Calendar] How to remove warning new version?Ramon: For the next 6 months or so. After that, Facebook will disable the old API interface completely and it will stop working.
As has been mentioned before, exporting to Facebook is NOT an Time.ly issue, but a Facebook API change that they didn’t warn anyone they were changing.
Also: Any new API credentials created since April DO NOT have access to the old API. If you deleted your existing Facebook API credentials (or had to re-create them), you will find that you will NO LONGER be able to post events to Facebook.