youtag

@ellmanncreative
THANK YOU FOR THE QUICK FIX !

hello @jonathandejong, I think I went without that functionality in the end but the site is not yet public for other reasons.

Thanks for your suggestion, it is very plausible. Just read that sql table names using a dash character need to be escaped with back ticks. I will try the fix and come back to you. Really love your plugin.

Thanks for your quick reply. I only saw it now, somehow the notification did not arrive.

I totally get you about the limited time. I have given up on trying to get the plugin to accept multiple terms.

Still hoping someone better than me will pick it up!

Meanwhile, I try to get the conditional fields working, but I will post that as a new topic …

yes, it’s under
settings > validation rules: Blacklist of extra IP addresses prior to country code.

to block entire countries, use the first setting (matching rule : blacklist)

I had the same issue. Debugged in Chrome, and found that the embedded code is blocked for security reasons:

Refused to display ‘https://prezi.com/embed/view/?bgcolor=ffffff&lock_to_path=0&autoplay=0&autohide_ctrls=0&html5=1’ in a frame because it set ‘X-Frame-Options’ to ‘sameorigin’.

Thanks @t-p. I was able to solve the problem by re-uploading all wordPress files. This time, I replaced the content of wp-admin and wp-includes folders rather than merging them with the new content.

The error, in my case, was due to either some files not being uploaded properly the first time or to non-replaced files causing the conflict.

I’m seeing the exact same issue on a site I manually upgraded.
Does anyone know where Class ‘Requests_Hooks’ is supposed to be defined?

mpraetzel, I was receiving fatal errors on the public site so I disabled it immediately without giving it too much thought. Probably the site didn’t have the latest version of PHP. The old version does perfectly well what it had to do, so I downgraded the plugin.

I know this is an old post, but I came here looking for the same answer. So I will share my solution, it might save someone else from searching through many files…

File is includes > classes > class-wpmmp-theme-handler.php

Change line 148
if ( is_admin() || current_user_can( 'manage_options' )
to
if ( is_admin() || current_user_can( 'edit_posts' )

This allows authors and editors to see the site while it remains hidden to subscribers.

Simple solution, hide the message via css:
.qtranxs-available-languages-message { display:none }

Thank you Keesiemeijer. I did not yet try your solution but I learned so much from you already. I’m sure it will be useful for other folks as this is a common problem when dealing with custom posts as events.

61pixels, thank you for confirming that it works. Feel free to post your specific code.

post A - dateFrom = 2014-06-05
post B - dateFrom = 2014-05-17, dateTo = 2014-06-28
post C - dateFrom = 2014-06-02

I expect the order to be B-C-A.

Currently it is C-A-B. It looks as though ORDERBY is using dateTo meta_value when present. I tried a lot of methods with the same result. Thank you for your time!

I had the exact same problem, and I came close to the solution thanks to keesiemeijer’s idea. Only thing bugging is that posts with end_date now get sorted by end_date instead of start_date. Perhaps this will help you.

I solved the problem thanks to this post by keesiemeijer

my query now looks like this:

add_filter( 'posts_where', 'start_date_posts_where' );

	$agenda_loop = new WP_Query( array(
	    'cat'   		=> $thisCatID,
	    'paged'			=> $paged,
	    'meta_key'   	=> 'dateFrom',
	    'orderby'     	=> 'meta_value',
	    'order'     	=> 'ASC'
	) );

	//echo $agenda_loop->request;

	remove_filter( 'posts_where', 'start_date_posts_where' );

I added the following function to my functions.php

function start_date_posts_where( $where ) {
	global $wpdb;

	$today = date('Y-m-d');

	$where = "
		AND  ($wpdb->postmeta.meta_key = 'dateTo'
		AND CAST($wpdb->postmeta.meta_value AS DATE) >= '$today')
		OR   ($wpdb->postmeta.meta_key = 'dateFrom'
		AND CAST($wpdb->postmeta.meta_value AS DATE) >= '$today')
	";
	return $where;
}

This results in the following query:

SELECT SQL_CALC_FOUND_ROWS cc_posts.ID FROM cc_posts INNER JOIN cc_term_relationships ON (cc_posts.ID = cc_term_relationships.object_id) INNER JOIN cc_postmeta ON (cc_posts.ID = cc_postmeta.post_id) WHERE 1=1 AND (cc_postmeta.meta_key = 'dateTo' AND CAST(cc_postmeta.meta_value AS DATE) >= '2014-05-24') OR (cc_postmeta.meta_key = 'dateFrom' AND CAST(cc_postmeta.meta_value AS DATE) >= '2014-05-24') GROUP BY cc_posts.ID ORDER BY cc_postmeta.meta_value ASC LIMIT 0, 10

This is close to what I want, only thing that bugs me is that posts with meta_key dateTo get sorted by dateTo instead of dateFrom.

* TinyMCE — TinyMCE went through a *major* update in 3.9: https://wp.me/p2AvED-2da. The new version (TinyMCE 4.0) introduces a much more modern and sane API, but some plugins written for TinyMCE 3.x will need some updates: https://www.tinymce.com/wiki.php/Tutorial:Migration_guide_from_3.x

qTranslate is hacking TinyMCE editor, so it looks like trouble ahead. It’s safest to disable WP updates before 3.9 is released.

Here’s the line to add in your wp-config.php for reference:
define( 'WP_AUTO_UPDATE_CORE', false );