[Barry]

Hi Alan. If you visit Events > Settings > Template can you note down what Events Template is set to and let me know (and even experiment with that a little)?

[Barry]

Hi Karen – it looks like you are using default (or “ugly”) permalinks. For the time being I am afraid our plugin simply doesn’t play nicely with that style of permalink and problems like you have described are not untypical.

Are you able to enable pretty permalinks?

[Barry]

Should I just add a line to the robots.txt file so that events are not crawled?

That’s totally up to you, I’d hope that if a 404 header is being returned then the search engine or whatever is doing the crawling would stop trying to access them.

I’m not really sure there is anything we can do to help with that, or that it is really a problem with our plugin as such – but we’re totally open to any feedback or suggestions you yourself might have on this one 🙂

As the month ends and there are 2 months left the pagination of the events goes down and maybe only paginates 7 times and then there are 404 errors for indexed pages for 8,9 & 10.

I visited the URL you posted when you created this thread but couldn’t find an example of this behaviour – could you provide a specific URL for me to look at?

Thanks!

[Barry]

Hi David!

If you visit Account Central > Downloads the release dates are indeed for the initial release of each plugin, but I am assured the relevant plugins which had hotfixes applied to them are indeed the ones you are now able to download.

I also tried to see if disabling the Pro plugin would make the issue go away – as the core ‘the events calendar’ is not affected – but the issue persisted.

I’m not sure the problem you are describing is something that the hotfix was intended to combat (columns missing in the events list) and it sounds rather different. Have you tried the regular troubleshooting steps of deactivating all other plugins – except of course for your Modern Tribe plugins – and at the same time reverting to a default, unmodified theme such as Twenty Twelve or Twenty Eleven?

[Barry]

You would need to assign the relevant capabilities to that user (or user role). For instance, the edit_posts capability is required to be able to allow editing of regular WP posts, whereas for The Events Calendar events the equivalent is edit_tribe_events.

Other basic capabilities are mapped out following the same pattern.

You may be able to use a role editing plugin to do this visually, otherwise you’d need to make use of the WordPress API.

[Barry]

No problem: you’d need to override the single-venue.php template and/or add some CSS, depending on what you’re most comfortable doing. Have you read our themer’s guide and tutorial on template overrides?

[Barry]

Hi Anne – so if you make the changes as directed here that would be great – they all relate to the Tribe_FB_Importer class found in the-events-calendar-facebook-importer/the-events-calendar-facebook-importer.php.

If you backup the original file so you can quickly restore it that would be a sensible precaution.

With those changes in place please visit the Import FB Events page – if (hopefully) there are events waiting to be imported (if there aren’t please create some) then you’ll see various bits of additional data displaying in the section headed Events from Facebook organizations(s) or page(s) you’ve added … ignore this!

Now, try to import an event or events and then look for similar output appearing at the top of the page (right at the top, above Import Facebook Events). If you could report back with a paste of that information that would be great.

If you need me to clarify anything please just ask. Thanks!

[Barry]

Not at all: by the by, if you don’t need all that HTML then it may be better from a performance issue to do things differently (I wasn’t sure if you wanted the whole gamut of HTML markup or not).

Individual functions like tribe_get_address() and tribe_get_city() could be used to build up a plain text string. They are called in any case further down the line when you use tribe_get_full_address() (which loads the full-address.php template) so this would be the cleaner and more efficient way of doing things.

[Barry]

Stop!! I do apologize, but I misled you there.

This one was not actually released as a hotfix. The developer looking into it did make a Gist available that you can use to patch your own plugin until the next version plugs the gap, though:

https://gist.github.com/3974181

That contains a new version of the get_facebook_photo() function which you can use to replace the existing one found in the Tribe_FB_Events class, which lives in the-events-calendar-facebook-importer/the-events-calendar-facebook-importer.php.

If you’re not quite comfortable with that then I’d ask that you hold off until the next monthly maintenance release comes along which will include this fix.

[Barry]

Formatting is still a bit off in my last post, but hopefully you get the gist: escape quotes in your string!

[Barry]

OK, so the template tag is returning a string that contains double quotes – so your address1 variable will contain >div itemprop= and the rest of that HTML will spill over and cause a syntax error.

So, what you need to do here if you want to capture and use all that HTML, is make sure that all of the double quotes are escaped. Or, in this particular scenario, you might just get away with using single quotes to define the string:

var address1 = '< ?php tribe_get_full_address(get_the_ID()); ?>';

Potentially though the same problem could occur at some point in the future, so escaping the double quotes is possibly the more robust solution here.

[Barry]

… Good example of how badly we need proper code formatting here! Let me try posting that again.

[Barry]

OK, so the template tag is returning a string that contains double quotes – so your address1 variable will contain

and the rest of that HTML will spill over and cause a syntax error.

So, what you need to do here if you want to capture and use all that HTML, is make sure that all of the double quotes are escaped. Or, in this particular scenario, you might just get away with using single quotes to define the string:

var address1 = '';

Potentially though the same problem could occur at some point in the future, so escaping the double quotes is possibly the more robust solution here.

[Barry]

Hi Mar. This sounds very much like a known problem and I believe it was solved in a hotfix (our reference for this problem is issue #18305) – so if you haven’t already done so, can I ask that you download a fresh copy of Facebook Events 1.0.3 and use it to replace your existing version.

(I realise you are already using 1.0.3, but for hotfixes the version doesn’t change even if some of the code does.)

Thanks!

[Barry]

Hi Anne … how confident are you in terms of playing with code? Do you think you’d be comfortable adding some lines to the core plugin code as part of the troubleshooting process or would you prefer that we do so directly (which would mean you’d need to provide access via (S)FTP or other means).

[Author]

Posts