[Barry]

Well, I’d prefer not to login to a live site for a number of reasons – but what could be worth exploring (since we’re on the verge of releasing a new and significantly changed version of the plugin) is trying out our latest beta code.

Of course this would ideally be done in a test environment – it isn’t “production ready” just yet – but it could be a good litmus test to see how well Canvas plays with that version – many of the biggest changes relate to theming and views, so there could certainly be a big improvement here.

If you want to take us up on that, please feel free to contact us using the details in the following post.

[Barry]

Hi Brad, that doesn’t sound good.

Ideally we’d get a sense for why these two plugins are colliding in the first place and then take things from there: based on your initial post it sounds like you are fairly comfortable with accessing the files in your WP installation via your hosting control panel – and this suggestion will rest on that – but if you feel uncomfortable doing this then let me know and we can consider other options.

So, please locate wp-config.php. Normally it is at the same level as WordPress itself (so if WP is installed in the webroot – something like /home/public_html/ – then you will find wp-config.php at /home/public_html/wp-config.php).

Open that up for editing and find the following line:

define('WP_DEBUG', false);

Change this to:

define('WP_DEBUG', true);

Then set about replicating the original problem. You may find that this exposes all sorts of different warnings and notices that are normally hidden, many of which may have nothing to do with this problem – so the idea would be to get to the point where both plugins are enabled and the dashboard “crashes” and take note of any errors that display at that point.

Fatal errors (and they will be labeled as such) are of particular interest.

With that done, change the WP_DEBUG setting back to its original value and post your results here and I’ll take a look 🙂

[Barry]

Right, so those are related and if you want different layouts for different views you might need to get creative.

One option could be to use the default event templates (ecp-page-template.php and ecp-single-template.php) and tweak them so the share the style and appearance of your theme – you could then either make one a two column layout (ecp-page-template.php) and the other something else, or, you could even make it so that a completely new template (ecp-two-column.php – you could call it whatever you wanted) loaded instead when certain conditions are met, such as it is an events page and also an archive page.

Does that sound like a workable plan here?

[Barry]

No problem. If it is indeed contained in a theme template file then perhaps you could copy it to your child theme and override it there? That way the original, core file would be untouched.

That’s just an idea, it’s difficult for me to offer concrete answers as Classipress is not a product I’m familiar with.

[Barry]

OK, so you are basically echoing out text instead of returning it – so it is never included in the string. Try changing:

tribe_get_organizer_link( tribe_get_event_meta( $post->ID, '_EventOrganizerID', true ) )

To:

tribe_get_organizer_link( tribe_get_event_meta( $post->ID, '_EventOrganizerID', true ), true, false )

[Barry]

It would also be interesting to learn what your PHP memory_limit setting is (ask your host if you are unsure) just in case the system is running out of juice while creating the PDFs.

[Barry]

Hi Carlos,

I’m not sure why you are experiencing this – but I wonder if you could try running through our standard troubleshooting steps in the first instance?

• Please ensure that your Modern Tribe plugins are up-to-date and in-synch … for instance if you are using The Events Calendar 2.0.11 you must also use Events Calendar PRO 2.0.11 (if you are using that plugin) and in this case WooTickets 1.0.1
• Deactivate all other plugins and change your theme to a default, unmodified one such as Twenty Eleven or Twenty Twelve
• Now test to see if the problem still exists
• If the problem has been solved by these steps, start reactivating everything one-at-a-time, testing at each point to see if the issue has returned
• If the issue does return, take note of whichever plugin (or theme) you reactivated immediately before it started again – it’s likely there is a conflict with this item

[Barry]

Hi Carlos, since you’ve already got a thread open here let’s keep the conversation flowing there, simply because if culturejam needs further support helping you both troubleshoot different environments could quickly become confusing.

[Barry]

If it helps at all, you can confirm this by looking at the source for your homepage where you will see:

<script type='text/javascript' src='http://winderdowntown.com/wp-content/themes/theme1541/js/jquery-1.6.4.min.js?ver=1.6.4'>

[Barry]

Hi!

You are currently running with jQuery 1.6.4 on your site. That is a comparatively old version of jQuery – by contrast, the current version of WordPress ships with 1.8.3 and that is the version that The Events Calendar expects.

You can find a summary of this issue in this thread – but note that it is not necessarily your theme which is causing this older version of jQuery to be used – it could be one of your plugins.

In the first instance it would definitely be worth exploring a switch to the shipped version of jQuery before we look at this further.

Thanks!

[Barry]

Well, it’s difficult to give a definitive answer because although the error refers to a file in their theme code the root cause could still lie within our plugin.

However, what we can say is that they are trying to use the result of a function and are assuming it is a string (a piece of text) without first checking to ensure that is actually the case – so it might be worth waiting to see what response they provide.

If it helps, do feel free to link to this thread from your support ticket with Classipress.

[Barry]

Excellent, well I’ll close this thread in that case – if anything else crops up please do feel free to create a new thread.

Thanks 😀

[Barry]

Hi! I can’t actually locate the problem in that screenshot … could you be a little more specific or, if you have the tools to do it, perhaps edit the screenshot and draw a big red circle around the problem?

[Barry]

If you’ve isolated this to your theme then we’d probably need to take a look at the actual error.

Are you able to access the server error logs (you might need to check with your web host on that one – unfortunately some hosts are limited in that regard)? If so then one strategy would be to replicate the error then check out the entries in the error log with the corresponding date/time.

Alternatively, you could try setting WP_DEBUG to TRUE (there’s a line in wp-config.php you would need to change):

define('WP_DEBUG', true);

Then visit the submit event page to trigger the problem and see if you are presented with an actual error message – but remember to restore the original value of WP_DEBUG afterwards.

[Barry]

Thanks Mike: for anyone else that might be interested in this, please do show your support at the above link.

[Author]

Posts