Forum Replies Created

Viewing 15 replies - 1 through 15 (of 292 total)
  • Thread Starter cefiar

    (@cefiar)

    Still no response form anyone at Time.ly about this. Even after I sent some emails to people who previously responded on the issue, things are suddenly silent.

    I’m happy to PAY for the ability to directly fetch feeds (like the plugin used to), rather than going through the Time.ly network.

    Issues with using the Time.ly network to me are:

    1. What happens if Time.ly’s network is unresponsive? We had that whole issue with the refer link thing that went bad (blocked by Google no less), so what’s to stop something similar happening to the feed service?

    2. If the connection between the website and the Time.ly network stops and there is no flow of traffic (eg: a network routing issue), there’s no event updates. There’s also no way I can debug the issue. This just adds another pathway that can fail causing my events not to update.

    3. If the feed sites block the Time.ly network from doing updates (due to rate limiting or whatever) there is no way to debug this.

    4. The fact that all the feeds are pulled through the Time.ly network means that the any possibly private data that is in the feeds goes through the Time.ly network. Some feeds I’ve set up in the past are firewall and access locked so that only the target sites can fetch them. Using the Time.ly network breaks that behaviour, and means I have to share such data with Time.ly. Some feeds are on internal networks (along with the WP/Time.ly install) and do not access anything in the outside world, meaning that I’d have to expressly poke holes in a secure environment to actually use the service, let alone that this private data would then be possibly in a 3rd parties hands.

    All of these are unacceptable things for the installs I’ve either managed in the past, or are currently managing.

    Thread Starter cefiar

    (@cefiar)

    I wasn’t even aware that they want to charge fees for feeds now. That is so not cool. You don’t take away features by moving them to a pay service.

    Welp, time to go looking for another solution.

    The behaviour you want is the default, so it seems you’ve got something set wrong.

    If you’ve set a date under Default calendar start date (optional) then it will always start from that date. Clear the date in there and you should restore the behaviour of using the current date.

    The easiest way to remove the categories selector is to hide it using CSS that you’ll need to add to your site (eg: using a plugin or the WP theme for your site). The CSS you want will depend on if you’re also using tags or not.

    If you’re not using tags, try:

    .ai1ec-calendar-toolbar {display:none}

    If you’re using tags, or have some other content that appears in the toolbar that you want to keep, try:

    .ai1ec-category-filter {display:none}

    Also, if you want to hide tags but keep categories, try:

    .ai1ec-tag-filter {display:none}

    Note: You may need to replace the none with none !important in the above CSS in some cases. I found this to be the case with the category & tag filters on my site, but not for the toolbar. YMMV.

    Happens to me too. Looks like the XSS fix may have busted the link to the tab. Definitely needs a fix.

    FWIW: It used to be /wp-admin/edit.php?post_type=ai1ec_event&page=all-in-one-event-calendar-settings#ai1ec-advanced but manually overriding to that doesn’t work either. The link on the tab is now giving me /wp-admin/edit.php?post_type=ai1ec_event&page=all-in-one-event-calendar-settings# which definitely doesn’t work.

    Sounds like a timezone issue.

    Check the timezone of the calendar you’re importing from, and also check the timezone set in WordPress ( Dashboard->Settings->General ) AND in Ai1ec ( Dashboard->Events->Settings–>Viewing Events ). If they are different, you will get a difference.

    In Ai1ec, you might also try the setting Display events in calendar time zone at the bottom of the Viewing Events tab, and then checking the details page for the event to see what it thinks the timezone is.

    After a further bit of testing I’m pretty sure this is down to PHP free memory. Without the Zend Opcode cache, PHP uses a lot more memory. I think this mainly just slows down stuff as things process in smaller chunks, freeing memory, then using it again.

    FWIW: The part of the page that was taking the most time (most of the 30+ secs was the main WordPress home page (the HTML output from the site root). To me, this implies this delay was either:

    1. All the changes to script and style enqueuing, which of course includes interaction with all plugins, themes, etc (and their memory usage requirements).
    2. Any post-processing of the HTML output (eg: compression, etc).

    Note: I still found this fairly true with most of plugins disabled on my site too, so #1 doesn’t seem to be quite so likely. At that point I backed off since it wasn’t getting me anywhere and I needed the site working. I upgraded the host to PHP 5.6 and since then, everything is fine with BWP active. I suspect I could debug this more by disabling the Zend Opcache in php 5.6 (for testing), but I’ve got a few other things I need to work on that have slightly higher priority ATM.

    Something of note that I found through testing:

    The plugin is really slow if your host is using php 5.4 or below, whereas if you’re using php 5.6+ it doesn’t seem to have any of these issues.

    I suspect this is mainly due to the new Zend Opcache code that is present in php 5.6 and up.

    FWIW: Rough values for a site I tried it on were:
    6.5-7 secs without bwp (php 5.4)
    30+ secs with bwp (php 5.4)
    5.5-6 secs without bwp (php 5.6)
    4.5-5 secs with bwp (php 5.6)

    I note that the weird text on that page appears to be base64 encoded, as base64 encoded info tends to end in an = sign.

    The encoded string is definitely out of Ai1ec’s venues section though.

    From memory: Ai1ec’s venues addon should add CSS to hide it from normal view, and Javascript that decodes this block.

    You could try going to Events->Settings–> Viewing Events tab and then clicking the “Save” button at the bottom of the page. Hopefully this will force the CSS/Javascript caches to rebuild with the correct info.

    1. All the navigation options can be hidden using CSS (almost everything has it’s own CSS tag). You will need a way to add CSS to your site (eg: via your WP theme or a plugin) to be able to customise this behaviour.

    2. Some of these are available via shortcodes. Look at “Shortcodes” under Events->Settings–>Advanced.

    The free version has a sidebar widget. The widget is not the same as the full calendar. It provides a limited view of events, rather than the complete calendar.

    You can also embed the calendar using shortcodes, so it’s possible to embed a specific view using a text widget and the shortcode. That said, you may need to modify the style of the view in that text widget using CSS, as most of the views expect a reasonable width for the view.

    This isn’t an issue with the plugin per se, but depends entirely on iThemes security’s interpretation of what “Filter Suspicious Query Stings” means.

    From brief exposure to this, it assumes that any query string that is passed to WP which is not a number or a common word is suspicious.

    Ai1ec encodes a lot of data in URLs that fetch event information, and it’s usually these that iThemes Security marks as bad. It encodes this information to reduce the length of the URL being fetched.

    Just to confirm here; it’s iThemes Security that is blocking you from accessing these URLs. I think you’d be better off trying to get iThemes to handle the issue so that their product handles such situations better, or includes an exception for what is obviously “known good” behavior that some plugins use.

    Best place to edit this information is to edit the language files, rather than editing the plugin directly. They’re located in the language\ directory of the plugin.

    Note: Updates will overwrite these files with newer versions, so you’ll want to re-do all your changes when you update (as the files will also change from version to version).

    Sounds like you’re using some sort of “Slider” plugin on your site that is incompatible with the plugin (looks like Rev Slider 2.4). I’d try disabling any slider plugins and see if the problem goes away to narrow it down.

    @offsider: Can you try your site with a different WP theme? I suspect that your WP theme may be the issue and need updating.

    Note: WP Theme, NOT calendar theme.

    You need to get your web host provider to increase the PHP memory limit for your website.

    Note: The amount you currently have is listed in the error message. eg: allocated 34865152 = 33.25MB (divide by 1048576 to go from bytes to megabytes). You most likely need at least 64MB for a standard setup.

Viewing 15 replies - 1 through 15 (of 292 total)