Home › Forums › Ticket Products › Event Tickets Plus › WordPress database error (Not unique table/alias)
- This topic has 10 replies, 3 voices, and was last updated 7 years, 10 months ago by
Dylan.
-
AuthorPosts
-
August 23, 2016 at 7:38 am #1154780
Dylan
ParticipantHello, I am getting a database error that looks to be caused by a conflict between the Event Tickets and the Powerpress plugins. It began showing up in the error log on June 24, 2016, but there are no noticeable problems on the front end. I just noticed today that my error log is 210 mb and found the error.
I found some posts about a similar error that was resolved in an earlier version of the Events Calendar plugin. Do you know how to fix this one? We sell tickets and publish podcasts for our shows, and these are two of our most-used plugins.
Thanks for help!
~~~~~~~
This is the full error:
[23-Aug-2016 14:17:53 UTC] WordPress database error Not unique table/alias: ‘wp_postmeta’ for query SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts INNER JOIN wp_postmeta ON ( wp_posts.ID = wp_postmeta.post_id ) INNER JOIN wp_postmeta ON wp_posts.ID = wp_postmeta.post_id WHERE 1=1 AND (
( wp_postmeta.meta_key = ‘_tribe_wooticket_event’ AND wp_postmeta.meta_value = ‘8369’ )
) AND wp_posts.post_type = ‘tribe_wooticket’ AND (wp_posts.post_status = ‘publish’) AND ( wp_postmeta.meta_key = ‘enclosure’ ) GROUP BY wp_posts.ID ORDER BY wp_posts.ID DESC LIMIT 0, 20 made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_feed, do_action(‘do_feed_podcast’), call_user_func_array, powerpress_do_podcast_feed, load_template, require_once(‘/plugins/powerpress/feed-podcast.php’), do_action(‘rss2_item’), call_user_func_array, powerpress_rss2_item, powerpress_get_the_exerpt, get_the_excerpt, apply_filters(‘get_the_excerpt’), call_user_func_array, wp_trim_excerpt, apply_filters(‘the_content’), call_user_func_array, Tribe__Tickets__Tickets_View->inject_link_template_the_content, Tribe__Tickets__Tickets_View->has_ticket_attendees, Tribe__Tickets__Tickets_View->get_event_attendees_by_order, Tribe__Tickets__Tickets::get_event_attendees, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->get_attendees, WP_Query->__construct, WP_Query->query, WP_Query->get_postsAugust 23, 2016 at 4:38 pm #1155122Andras
KeymasterHi Heather,
I’m sorry you are experiencing this issue. Let me try to help you out with this.
Could you share with me the link to the thread with the similar error please?
Do you still get this error if you deactivate Powerpress? Or if you deactivate The Events Calendar Plugins and leave Powerpress on? Would be great if you could test this, that could shed some light on things.
I’ll be waiting for the results.
Cheers,
AndrasAugust 26, 2016 at 9:09 am #1156369Dylan
ParticipantHi Andras, here are the previous posts I found with this error. These appear to have been fixed in version 3.4 of The Events Calendar:
I have tried to recreate the error so I can deactivate the plugins and test it, but I can’t track down the exact trigger for the error. The last error happened today at 14:10:26 UTC (about two hours ago as I type this). Since then I have browsed the site trying to trigger the error and haven’t gotten it. I went to posts with tickets, posts with podcasts, played podcasts, put tickets in the cart, navigated the related admin areas etc, and none of that triggered the error. I even played the podcast in iTunes and no error occurred.
I did identify that the error is tied to our podcast feed, which displays 20 episodes at a time. Every time the error happens the error log shows multiple errors for each of the 20 posts that contain podcasts. I cannot figure out how these relate to the The Events Calendar tickets unless they are sharing table names or some other database weirdness.
I would like to share a file with the last batch of errors, but the forum won’t let me upload a text file. I have attached a screenshot of a portion of the file, where you can see multiple errors for one of the 20 posts. The total batch of errors that happened at 14:10:26 UTC today has 480 lines of error code. The errors happen anywhere from five minutes apart to several hours apart, and each one includes this massive amount of code, so our error log is now several hundred megabytes.
Thanks for any input you have.
August 29, 2016 at 3:38 pm #1157313Andras
KeymasterHi Heather,
So far I haven’t been able to reproduce the issue. I will keep testing a bit.
If you happen to come across the trigger, please share with me. This could be a bug and that might help us eliminate it.
Apart from the error log do you get other notifications of this error? Is it visible on the front-end / back-end of your site? Do you have WP_DEBUG in wp-config.php enabled or disabled?
Thanks,
AndrasSeptember 1, 2016 at 8:55 am #1158789Dylan
ParticipantHello Andras, the error log is the only sign of this issue. Nothing odd shows up on the front or backend and the podcast works fine. WP_Debug is turned off.
The downside is that our error log grows several megabytes every day because of all the errors. The last one happened today at 12:47:20 UT, about 3 hours ago.
Perhaps I should post a question to powerpress tech support to see if they have encountered the issue.
September 1, 2016 at 2:03 pm #1158998Andras
KeymasterHello Heather,
Thanks for getting back to me on that.
This might be a legit issue. In order to investigate, could you share with us a database dump?
I believe as long as you don’t see any issues on your website, it shouldn’t be a big problem for the time being. But we’ll look into it. I ask for your patience (and your database dump 🙂 ).
Thanks and cheers,
AndrasSeptember 6, 2016 at 7:55 am #1160346Dylan
ParticipantHi Andras, I tried to attach the database sql file but get an error message that it is too big (22mb). Is there a better way to send it to you?
September 6, 2016 at 2:16 pm #1160640Andras
KeymasterThis reply is private.
September 7, 2016 at 6:29 am #1160882Dylan
ParticipantThis reply is private.
September 7, 2016 at 8:00 am #1160927Andras
KeymasterThis reply is private.
May 31, 2018 at 4:37 pm #1543431Victor
MemberHi Heather!
Just wanted to share with you that a new release of our plugins is out. As of this version, and possibly earlier versions too, we can no longer reproduce the issue described in this ticket.
You can find out more about this release → https://theeventscalendar.com/maintenance-release-for-the-week-of-27-may-2018/
Please update the plugins and let us know if this works for your site too.
Best,
VictorJune 22, 2018 at 9:35 am #1559347Support Droid
KeymasterHey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.
Thanks so much!
The Events Calendar Support Team -
AuthorPosts
- The topic ‘WordPress database error (Not unique table/alias)’ is closed to new replies.
