sfbarth

Thanks for the reply! I didn’t realize that, because individual Youtube videos work just fine. When inserting a playlist of youtube videos in the backend, it would be helpful if the plugin indicated that this won’t work without the pro license.
I’ll talk to the customer about purchasing a license.
??

Excellent, seems to be perfect now!
Thank you for the speedy reply and update ??
When the site goes live, I won’t forget to rate your plugin and donate.

Cheers, Stefan

Thanks! Adding the parameter 100 did it!
(Tried

add_action( 'after_setup_theme', 'nilsplanet_setup' );
function nilsplanet_setup() { ...

before.)
??
Cheers, Stefan

Hi Shelby,
I just updated everything (WP 4.7.1, Events Calendar 4.4.0.1), but the error persists:
Fehler:
[The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay]
SELECT SQL_CALC_FOUND_ROWS DISTINCT wp16KW_posts.*, tribe_event_start_date.meta_value as EventStartDate, tribe_event_end_date.meta_value as EventEndDate FROM wp16KW_posts LEFT JOIN wp16KW_postmeta as tribe_event_end_date ON ( wp16KW_posts.ID = tribe_event_end_date.post_id AND tribe_event_end_date.meta_key = ‘_EventEndDate’ ) LEFT JOIN wp16KW_postmeta AS tribe_event_start_date ON wp16KW_posts.ID = tribe_event_start_date.post_id AND tribe_event_start_date.meta_key = ‘_EventStartDate’ WHERE 1=1 AND wp16KW_posts.post_type = ‘tribe_events’ AND (wp16KW_posts.post_status = ‘publish’ OR wp16KW_posts.post_status = ‘tribe-ea-success’ OR wp16KW_posts.post_status = ‘tribe-ea-failed’ OR wp16KW_posts.post_status = ‘tribe-ea-schedule’ OR wp16KW_posts.post_status = ‘tribe-ea-pending’ OR wp16KW_posts.post_status = ‘tribe-ea-draft’ OR wp16KW_posts.post_status = ‘future’ OR wp16KW_posts.post_status = ‘draft’ OR wp16KW_posts.post_status = ‘pending’ OR wp16KW_posts.post_status = ‘private’) ORDER BY tribe_event_start_date.meta_value DESC, tribe_event_end_date.meta_value DESC, wp16KW_posts.post_date DESC LIMIT 0, 20

WordPress-Datenbank-Fehler:
[The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay]
SELECT SQL_CALC_FOUND_ROWS DISTINCT wp16KW_posts.ID FROM wp16KW_posts LEFT JOIN wp16KW_postmeta as tribe_event_end_date ON ( wp16KW_posts.ID = tribe_event_end_date.post_id AND tribe_event_end_date.meta_key = ‘_EventEndDate’ ) LEFT JOIN wp16KW_postmeta AS tribe_event_start_date ON wp16KW_posts.ID = tribe_event_start_date.post_id AND tribe_event_start_date.meta_key = ‘_EventStartDate’ WHERE 1=1 AND wp16KW_posts.post_type = ‘tribe_events’ AND ((wp16KW_posts.post_status = ‘tribe-ignored’)) ORDER BY tribe_event_start_date.meta_value DESC, tribe_event_end_date.meta_value DESC, wp16KW_posts.post_date DESC LIMIT 0, 10

Maybe the file src/Tribe/Admin_List.php would be the place to insert SET SQL_BIG_SELECTS=1? I’m not that much of a programmer … However it seems you’re using WP_Query, and I’m not sure where and how to alter that. Any suggestions?

Thanks!
??
Stefan

Thanks for checking back, and all the best for 2017! ??
You’re right, it still is a busy time, and I haven’t had a chance to deal with this.
Just to clarify:
1. I could not turn on PHP7, but not because of YOUR plugin, but an other one the client needs.
2. With PHP 5.6 and debugging turned on, I get the error message mentioned above, related to MAX_JOIN_SIZE
3. This is all still version 4.3.5 of your plugin.

Next thing I’ll make backups and then update the plugin. If the problem persists, I’ll try to put in SET SQL_BIG_SELECTS=1.
Of course, if you could point me to the relevant line in your code, that would be helpful!

Since this probably is back end only, I’m not concerned about higher load/performance issues.

Cheers, Stefan

Hi Shelby,

I tried the update, but found another plugin is incompatible with PHP7. So I did what I should have done first, and turned on WordPress debugging. The error is:
WordPress-Datenbank-Fehler: [The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay]
SELECT SQL_CALC_FOUND_ROWS DISTINCT wp16KW_posts.ID FROM wp16KW_posts LEFT JOIN wp16KW_postmeta as tribe_event_end_date ON ( wp16KW_posts.ID = tribe_event_end_date.post_id AND tribe_event_end_date.meta_key = ‘_EventEndDate’ ) LEFT JOIN wp16KW_postmeta AS tribe_event_start_date ON wp16KW_posts.ID = tribe_event_start_date.post_id AND tribe_event_start_date.meta_key = ‘_EventStartDate’ WHERE 1=1 AND wp16KW_posts.post_type = ‘tribe_events’ AND ((wp16KW_posts.post_status = ‘tribe-ignored’)) ORDER BY tribe_event_start_date.meta_value DESC, tribe_event_end_date.meta_value DESC, wp16KW_posts.post_date DESC LIMIT 0, 10

So I presumably have MAX_JOIN_SIZE set higher locally than on the provider’s server (shared hosting). I’ll leave it for the time being and try again when I have a little spare time.

Thanks, and a happy holiday season!
Stefan

Hi Shelby,

thanks for your reply!
??
However, the server is running the newer version. I can change upwards to version 7, but not downwards. Do you reckon that might help?
In the meantime I’ll turn on debug mode and see what happens.

Cheers, Stefan

Hi Matt, glad to see you’re active again in the support forum! Maybe you could have a look at my problem, too?
Thanks!
??
Stefan

I have the problem only where the domain name entered doesn’t match the name stored in WordPress. Like, wordpress is installed in xyz.de, but the xyz.com points to the same directory. Seems like a security measure to me. If that’s the case, it would be neat to have an option to enter ‘legal’ domain names.

Strange: in Hyphenator_debug.js the alert is triggered on line 342 (v. 4.1.0)
onError = function (e) { window.alert ...
in the Hyphenator.js it seems to turn into
b=function(t){e.alert( ... on line 61

I don’t know enough javascript – none, really ?? – to make sense of this.

Hi Vasyl,
From my development site (WP 3.3.1, AAM 1.5.8.2 beta):
1. Administrators other than me have access to back end. Only AAM-page remains blank. (That is, it shows the menu on the left, the menu item ‘AAM Group’ is highligthed in gray, the footer ist visible. The submenu item ‘Access Manager’ doesn’t show and the area for making AAM settings is blank.)

I just noticed the capability ‘AAM Manage’ had disappeared in the update, adding it again for Administrators gives them access to AAM as before.
So that appears to be fine!

2. Editors w/ restricted rights can now put a post in the trash, restore or delete it; perfect! ??

Stefan

Great! I’ll try it on my development site a.s.a.p. and report back.
Cheers, Stefan

Thanks for the quick reply! I’m looking forward to the next releases!
??
Cheers, Stefan

I just had that same problem and got around it following the suggestion of Club6 elsewhere in the forums.
Simply switching the language to English made the systems to choose from visible!