[Joey Kudish]

Great, thanks Caleb. I’ll try to reproduce the issue on my test site and see if I can find a resolution. I’ll be in touch soon.

Thanks

[Joey Kudish]

Hi Caleb,

I’m the developer who worked on this particular issue with the 2.0.3 release. I’d like to help you troubleshoot this. Can you please confirm that you are running WordPress 3.3.1, and The Events Calendar 2.0.3 and The Events Calendar Pro 2.0.3 – I want to rule out any possibilities of out of date core/plugin before I dig deeper?

Let me know and if needed, I’ll look into it some more.

Thanks,
Joey

[Joey Kudish]

Hi everyone,

Thanks for finding the solution Andy and sharing it with everyone one. You are absolutely correct in that it’s the version of iCalendar and not of our plugin. We must of accidentally changed this when releasing version 2.0.3. We’ll make sure to have that fixed in 2.1 which is our next release and we’ll let other users know of the solution.

Thanks again,
Joey

[Joey Kudish]

Hi Karen,

I’m the dev that Rob passed the issue along to. I am trying to make sense of the error/issues you are experiencing but I am not 100% sure I understood from your explanation what is going on. I’ve also asked Rob to send along the log file that you sent him, so that I could take a look.

* What exactly are the errors or issues you are seeing? Can you provide us with screenshots or anything that could better show the situation?
* Who is your host?
* When your host shut down your site, did they say why?

I’ve subscribed myself to this forum post and I’ll respond as soon as I hear back from you or when I receive the log files from Rob.

Thanks
Joey

[Joey Kudish]

Hi,

There’s a number of different ways to target the pages generated by the plugin using css. Glad to hear you found one of them Corey!

As Rob mentioned, the issue of not having a page ID will be solved in 2.1 as we plan to make the page a real page rather than a “pseudo-page”.

Cheers,
Joey

[Joey Kudish]

Hi Jaki,

I’m the dev who’s looking at your issue.

* I just logged in and I wasn’t able to recreate any errors after poking around for a few minutes. Is there anything specific to do to recreate the errors you are seeing?
* Please delete the eventspro account or at least change it’s password, anyone on our forums can see your username and password, which I am certain is not something you want. If you want us to have access to the site, please email your credentials to [email protected] – very important! 🙂
* A word of caution for any “profiling plugin” – while I am not familiar with the specific one you are using; in my experience the vast majority of such plugins add more overhead than they save you. I would advise against using them. It also seems that the one you are using is made specifically for Go Daddy hosting, but you are using Rackspace, so the results may not be conclusive. Finally, yes, both our plugins currently add the most overhead to your site, but considering the other plugins you are running are smaller, it’s perfectly normal. The amount of runtime seconds that the profiler is reporting isn’t high and falls in our usual benchmarks. Your total plugin loading time is 0.626 which is quite within norms.
* Finally, I noticed that you are running version 2.0.2 of our plugins. Can you upgrade to 2.0.3 to rule out the possibility that we’ve already fixed the issue(s) you are experiencing?

As I said, I wasn’t able to recreate the issue(s), but we are ready to help if you can first upgrade to 2.0.3 and then provide further details 🙂

Thanks & have a great day!
Joey

[Joey Kudish]

Hey Everyone,

I’ve personally looked at the issue and the code that generates the error, and as best I can tell we’re doing everything right on our side. I’ve now gotten in touch with the team that runs the Gantry theme framework to see how we can resolve this together if need be. I’ll keep you guys posted and I apologize about the issues!

Cheers
Joey

[Joey Kudish]

Regarding the first gist, I was just trying to show you what changed. In the second gist, I pasted the whole file… Sorry about any confusion there.

[Joey Kudish]

Hi Timothy,

According to Google’s Webmaster Tools FAQ, there is no way to remove the errors, however they will not negatively impact your rankings. See: https://sites.google.com/site/webmasterhelpforum/en/faq–webmaster-tools#404-errors-2

Cheers

[Joey Kudish]

Hi Vincent,

Yes, you can remove all events directly from the database.

WARNING: BACKUP your database before you do this. Seriously, back it up. I don’t want you to accidentally lose anything in your database. Also, please understand that you are doing this at your own risk, we don’t usually encourage users to manipulate the database directly and can’t provide support for doing this. But we’ll happily provide guidance.

Ok now that the warning is out of the way 🙂
I’ll give you the longer answer with the explanation and then the SQL command you can run to delete them all.

Events are a custom post type within WordPress, which means that they are stored in the posts table along with all other posts, pages and other custom post types. The way to differentiate them from other posts, is with the ‘post_type’ column. Events registered with The Events Calendar will have ‘tribe_events’ as their post type. So your goal here is to delete all entries from the posts table with the ‘tribe_events’ ‘post_type’. So here’s the SQL you can run directly from phpMyAdmin:


DELETE FROM wp_posts WHERE post_type = 'tribe_events'


Note: you may need to change wp_posts to customprefix_posts if your table prefix is different (as defined when you installed WordPress)

Again, this is quite an advanced request and we advise you to act with caution and backup first 🙂

Hope this helps, let us know if you have any further questions.

Cheers,
Joey

[Joey Kudish]

Hi Timothy,

If your calendar disappeared, it’s most likely because you overwrote too much of the file or didn’t do it properly. Here’s exactly what you should do. This will require you using FTP to access your files (this is beyond what we can help you with, but your host may be able to – if need be)

* In your theme folder (wp-content/themes/{the name of your theme}), create a new folder called “events”
* In it, create a new file called table.php
* In that file paste the following: https://gist.github.com/043fe74f30cd04e07ec5 (make sure to grab the “raw” code)

As Rob mentioned, this issue will also be fixed in the 2.1 release that we’re currently working on. The “fix” I am suggesting is only temporary and exceptional for your situation.

Let me know if this helps.

Cheers,
Joey

[Joey Kudish]

Hi Jason,

I am a little bit unclear as to what exactly you are trying to do. Can you specify in more details what you’re trying to do and any code you have already written (beyond the var_dump).

I’ll wait to hear back, and then I should be able to assist you with this.

Thanks,
Joey

[Joey Kudish]

You will need to turn on “Pretty Permalinks”, more information on that here: http://codex.wordpress.org/Using_Permalinks#Choosing_your_permalink_structure

That will make the URL be sitename.com/events, you can change the “events” part under Settings > The Events Calendar.

Let us know if you need anything else!

[Joey Kudish]

Great, glad you figured it out Jason!

[Joey Kudish]

Hi Xpert,

I apologize for mis-understanding your request and thanks for clarifying. You can accomplish this by

You need to overwrite the views/table-mini.php (from the plugin folder) by adding a new folder named ‘events’ inside your theme and copying that file in it. Then you will have to modify it based on the following code https://gist.github.com/b37552eee9efcc0a53a5. Inside the code, I added comments to the lines you will need to modify, specifically lines 71, and 86-100. Please note that the tribe_get_linked_day() function which generates the link for each day is a PRO function, so you will need the PRO version of the plugin activated for this to work.

I’m going to check with the rest of the team, but if everyone agrees, we’ll add this in as a feature by default for the upcoming 2.1 update.

Cheers

[Author]

Posts