Error when event is set to reoccur when set to daily or weekly or custom

[Francisco]

I have recently purchased the PRO version of the events calendar and had it installed on a fresh installation of WordPress. When I try to create a new event that is reoccurring (daily, weekly, or custom), it shows up with errors on the page. I have not customized anything on this installation.

Here’s a direct link to show the errors:
http://tamtruong.com/tribetestblog3/?tribe_events=al-anon&eventDate=2012-02-17

(This is the error message)
Warning: Missing argument 2 for TribeEvents::addDateToRecurringEvents() in /home/tamtruon/public_html/tribetestblog3/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php on line 413

[Rob]

Odd error; thanks for reporting it, Francisco. I’m unable to recreate this with the same code so my guess is there’s something else at play here. Let me see if our dev Jonah can identify what it may be via the error message itself. I’ll get him to respond directly if so.

[Francisco]

Thanks for your prompt response, Rob. I believe the error only shows when I post a reoccurring event that is daily, weekly, or custom. It seems to work fine when I post as monthly or yearly.

[Rob]

Ah, good to know. And have you been able to test deactivation of other plugins to make sure nothing is conflicting there? Just wanted to make sure.

[Francisco]

Rob, yes I have no other plugins installed while the error is showing.

I’ve noticed this initially while using a work-in-progress WP project. But just to rule out any conflicts I did a new fresh WP installation and added the calendar pro plugin to replicate the problem… sure enough it was there again.

[Jonah]

Hey Francisco, I was also unable to reproduce this and am not sure what it could be. I’m going to get one of the other devs to take a look.

Thanks,
Jonah

[Francisco]

Thanks Jonah,

Could this be an issue with the way WordPress is installed on my web server? I used an auto installer in my cpanel (Installatron) out of convenience… tomorrow I will try to do another fresh install manually to see if that works.

[Jonah]

Not sure, I wouldn’t think so though. It might be related to something on the server – PHP/MySQL versions, server memory so I would make sure PHP/MySQL are up to date (but they probably are if you’re running the latest version of WP) and try upping the server memory via .htaccess or php.ini to at least 64mb… other than that I don’t know. I’m going to get one of the other devs to step in and take a look.

[Joey Kudish]

Hi Francisco,

I’m one of the more advanced devs on the team here, and am going to try to help you debug this issue.

First of all, I am not able to duplicate it on my installation either, so it has to be something specific to your installation.

Secondly, since this is a PHP warning and not a fatal error, you can actually hide it (which wouldn’t be exactly a solution, but would at least hide the issue from your visitors). You shouldn’t be showing PHP errors on a production site any ways because it’s a potential security risk (though it can be handy to see the errors on a development site – especially if you are a developer). First, please make sure that WP_DEBUG is set to ‘false’ in your wp-config.php file, the line should like this:


define('WP_DEBUG', false);


If the error still appears after setting that, you can add the following line to your .htaccess file (make sure it is on it’s own line:


php_flag display_errors off


Now to actually fix the issue (hiding it isn’t enough)… I would like to be able to access your site/server directly. Can you send a set of credentials for the wp-admin and FTP if possible to rob [at] tri.be and he’ll forward that along to me so we can troubleshoot this further.

Hopefully, by collaborating. we can get this sorted out. Let me know if you have any other questions!

[Joey Kudish]

Just a note, when/if you do send your credentials to Rob, please include a link to this thread in the email so that he knows what it’s about 🙂

Thanks!

[Joey Kudish]

Hi again,

We received your credentials and I was able to investigate this further. The errors were only appearing because you had left the permalink rules (under Settings > Permalinks) to default. Changing the rules to anything else made the errors go away. We strongly recommend you use permalinks in your site (not just because of our plugin, but also for SEO reasons and because it just looks proper). That being said, we do want to fix this issue anyway, so I’ve now logged it so we can fix it in a future release.

Thanks

[Francisco]

Guys,

Much thanks for the super quick help! That seems to have fixed the errors 🙂

[Rob]

Excellent to hear, Francisco. Thanks for confirming as much – if anything else arises or if you need anything else here please let us know.

[J T]

Thanks for this, solved my problem as well.

[Rob]

Awesome! Two birds with one stone. Thanks for the heads up JT!

[Author]

Posts