Forum Replies Created

Viewing 15 replies - 1 through 15 (of 22 total)
  • So for those of us who encountered the same problem, and used brute force means to disable the plugin but have not deleted, what is the recommended recovery?

    I encountered the problem with an ordinary calendar, not a grouped calendar. I got past it by changing timezones settings and then going back to the default timezone (under advanced settings).

    Troubleshooting was complicated by presence of a WP cache in addition to the calendar plugin caching.

    If you have events show up on the wrong day, be sure to check the event’s start and end times – I found that my event’s times were whacked. They were time-shifted (suggesting a timezone issue). Start times shifted from early evening to after Midnight resulted in an event showing up the following date – which at least makes some sense.

    I’m also having events show up on the grid view a day late. I suspect a timezone issue, because the times listed for the event are incorrect (don’t match the google calendar event). I’ve tried setting both Default timezone and also my local zone (Eastern). No success. (Yes, this was a Google Calendar Events upgrade.)

    Importantly, the Preview display in the calendar editor is correct, but the one displayed on the actual website is not. I’ve cleared cache, but no success.

    This is causing real chaos, so any help would be most appreciated!

    Update: My situation was complicated by another WordPress cache. I cleared that, and now the website matches the preview.

    My event times and dates are now showing correct. I suspect what fixed the problem was going to Calendar advanced settings, changing the time zone to my local, then change it back to default. Hope this helps others!

    2.1.6.1 fixed my problems with Grid view’s Prev and Next. Thank you!

    jbenni

    (@jbenni)

    I have also been having problems with Prev and Next, from the Grid view.

    In 2.1.3 I was able to eliminate an error message by commenting out the code that does a “Die” after nonce checking in Misc-Functions.php.

    I saw that version 2.1.4 had code changes in this area, but Next/Prev still fail for me – however the symptom is different now. It displays “-1”.

    I have reverted to my patched version of 2.1.3, so that my site functions.

    Is there anything I can do to help troubleshoot and/or eliminate this problem? Thanks!

    jbenni

    (@jbenni)

    Commenting out the two die ('Request has failed'); lines in misc-functions.php (one for the grid layout, another in the same file for other layouts) does seem to provide a reliable workaround.

    I speculate that the problem is a nonce is cached and kept past its expiration date. Which explains why it works initially (the cache is fresh) but fails later.

    I hope this helps the developers zoom in on the cause and provide a real fix for this quickly.

    jbenni

    (@jbenni)

    I dug into the code a bit, and found that I could get Next/Back to work by commenting out line 113 of “/includes/misc-functions.php” so that it looks like this:
    // die ( 'Request has failed');

    That line appears to be a bailout after checking a nonce, but the condition seems non-fatal. I don’t suggest this as a real fix, rather just a helpful hint to the developers…

    Keep up the good work.

    jbenni

    (@jbenni)

    After reverting to 2.1.1 the problem persists. It may be an intermittent problem – this version worked previously but both it and the newest (2.1.2) fail now.

    jbenni

    (@jbenni)

    V 2.1.2 generates “Request has failed.” in response to Next and Back buttons in Grid mode.

    I’m pretty certain V 2.1.1 worked properly. How to revert?

    Problem resolved, thanks. I did the uninstall, ignored the WP warning about deleting data, and then re-installed. Happily, my feeds survived.

    Then I (finally) saw the Retrieve From/Retrieve Until – which allowed me to get the desired result.

    What about a “Retrieve Until” setting for “1 year hence”?

    Anyway case closed. Thanks again.

    Same question – must we reconstruct our calendar links to resolve issues with max=?

    With 2.0.3.1 I have the same issue – I need to increase the number of events displayed. The feature stopped working recently, and as of today’s release (2.0.3.1) the behavior has changed but still isn’t right. I use a shortcode like this: [gcall= "1234" max="150"].

    I get a calendar grid as expected. In today’s version, when I “Next>>” a couple of months ahead to a point that exceeds the default small event limit, the calendar display disappears.

    In yesterday’s version (2.0.3), the Calendar remained but the “Next>>” button disappeared when the default (low) number of events was displayed.

    What I need is to have the “Next>>” button remain in place to allow advancing until the specified number of events has been displayed. In my case, I want the calendar to be visible up to a year in advance, for scheduling about 20 events per month.

    I know the author has been working on the code in this area, and appreciate the prompt responses. It’s not quite right, but clearly getting close.

    Thread Starter jbenni

    (@jbenni)

    I got another report of invalid RSS feed from a user who uses Thunderbird. When I check my RSS feed at Feedvalidator, it validates but issues a warning/recommendation:

    This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
    Feeds should not be served with the “text/html” media type

    What is the expected Mime type for WP RSS 2.7.1? And if it isn’t ‘application/rss+xml’, is there a reason?

    Thanks,
    John

    Thread Starter jbenni

    (@jbenni)

    Thanks mucho.

    I moved the widgets to the plugins folder and deleted the widgets folder. All seems to be working now.

    Thanks again, case closed.

    Thread Starter jbenni

    (@jbenni)

    Okay, I agree that “view source” for the RSS page is a good way to observe the presence or absence of the white space in the feed. Thanks for your attention on this.

    I’m still stuck with a sneaky intermittent problem and the old adage that “absence of evidence is not evidence of absence”. I’ll wait for more reports to roll in and look for patterns.

    press on!
    J.

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