evilcrusher

I was getting this very same issue and it took me a moment to realize what I did wrong. I was using just https://yoursitename.tld

In the app setting you need the site url to be https://yoursitename.api.oneall.com –

The same goes for the app domain.

Remember that you must use the https:// function in front of the url.

The easiest way to find out what your url would be is to go back to the setup instructions for that connection and copy/paste that url into the needed fields.

I think the OneAll site needs to update the directions as Facebook has changed the order and placement on how this is setup.

Thankyou. If I get this working, I will post directions on this fix to other users who have asked. If that is ok.

Edit, yeah I couldn’t figure out what code is actually needed in the wpdb or what needed to be in the line for the voting function php file.

The voting function php file states:

$items = $wpdb->query($wpdb->prepare("SELECT * FROM ".$wpdb->prefix."wpv_voting_meta"));

and the wpdp file code that it is trying to access states :

function prepare( $query, $args ) {
		if ( is_null( $query ) )
			return;

		$args = func_get_args();
		array_shift( $args );
		// If args were passed as an array (as in vsprintf), move them up
		if ( isset( $args[0] ) && is_array($args[0]) )
			$args = $args[0];
		$query = str_replace( "'%s'", '%s', $query ); // in case someone mistakenly already singlequoted it
		$query = str_replace( '"%s"', '%s', $query ); // doublequote unquoting
		$query = preg_replace( '|(?<!%)%f|' , '%F', $query ); // Force floats to be locale unaware
		$query = preg_replace( '|(?<!%)%s|', "'%s'", $query ); // quote the strings, avoiding escaped strings like %%s
		array_walk( $args, array( $this, 'escape_by_ref' ) );
		return @vsprintf( $query, $args );
	}

Same thing here using Magazino v1.1.2

From what I’m finding, no one got ready for this. Not even other big social media sites such as twitter. I put my twitter settings to post to my facebook page to try to work around this and it can’t even do it. Jgentes is right about this.

I forgot myself that this past weekend, Facebook implemented developers changes. One of the big ones was to use absolute hrefs if I recall correctly. So this really boils down to not paying attention to what Facebook put out over 2 months ago. There is probably lots of code that needs to be changed to get this to work with how Facebook changed, but really – everyone had plenty of time to prepare for this. It was not like Facebook said “Hey we are gonna do this, and it starts tomorrow!” I guess I will sit and wait patiently to hear about an update cause that is what I really believe is going to fix this issue.

Nevermind. Out of the blue it has started working. I’ll know for sure tomorrow when I post again.

Posting because I need updates as well. I’m going to have to check to see if there is a thread about another issue that occurred the same exact time this issue did. My connection to Tumblr is showing up in the settings, but the posts don’t make it to the blog. ??

Thank you very much Funstix. That was the answer is needed and has solved my problem.

kymar
Member
Posted 1 month ago #

OK – mrmonster – not sure why this happens, maybe if you “just once” resize your editing box to very large, you get stuck in a loop

but this works for now at least as a hack:

in the includes/class-wp-editor.php file you’ll find

Line 74: elseif ( $set[‘editor_height’] > 5000 )
Line 75: $set[‘editor_height’] = 5000;
if you change the last 5000 on line 75 to a smaller number – say 300 or whatever you prefer – then save the file, the ginormous box will re-size to that height.

May later look at more elaborate fixes or commenting out more code, unless someone who KNOWS comes along with a real fix.

I tried the plugins and the update. Neither worked. Tried in IE cause Im using Chrome. Didn’t fix it.

Just saw this, how can I get the default area to be smaller? Mine is defaulting to being roughly 3 to 4 pages long upon writing new articles?

On another note,I don’t even think 3.4 has been out for over 6 months. So why was 3.5 in beta testing when 3.4 wasn’t even released?

https://frickinexcuse.net/escort-missions-are-retarded/ This page gets the same warning for me, I look at the pages source and see that there are in fact 3 h2 tags in the source. Visual editor is enabled and I am having a problem with that. I just installed this plugin yesterday and love the majority of it. Just getting errors when the keywords are one letter off like an s at the end. Any help would be appreciated.

I wound up using simple facebook connect which is not giving me this error at all. I needed a solution now, and looking at the facebook stock, it appears that they have other worries on their plate right now.

Tried the new version of 1.0.3 and still no luck. I only have the disabled option for posting to a page. I look into the whole app thing and facebook states that only if the app supports pages. What I don’t get is if the plugin doesn’t really use the facebook app for anything, then why is it needed? What do I need to do to even have the enabled option come up for this.