Cheating message even when posting as Admin

Hi Jonga,

Haven’t had this problem myself. I’m about to release the 4.3 version of the development release within a day once I’ve finished a few more tests. I will get you to try it just in case it solves your problems.

Hi Jonga,

My new development version 4.3 passed my remaining tests in no time and is now released. Give it a try to see if it solves your problems.

Hi prof,

Have updated your dev version 4.3 although support page in admin is still showing version as 4.2 – which I suppose could indicate I haven’t updated correctly. Although remote files show correct 4.3 version.

Anyway, I am getting the same issue as described above. I seem to think all my issues in this thread and the one before where we’ve been discussing are to do with permissions. The behaviour is as if I don’t have permissions to upload images or post. I am using plugin s2member but have tried disabling all plugins and still getting this CHEATING? message and no images will upload or select via the Add Media or the Upload button.

J.

Hi Jonga1306,

You probably have updated fine as I just checked my support page and found my version number is still 4.2. So congratulations for finding the first bug. I have two cans of insecticide in front of me as I type and are in a dilemma as to which one to use :).

As to your dilemma in order to further define the problem try doing the following.

1. Disable all plugins including s2member

2. Clean out the cache of your browser just in case an old javascript file is causing the problem

Try uploading as admin using the following three methods (you did mention some of this above but just making sure).

3. Featured image upload.
4. Editor ‘Insert Media’ upload
5. Attachment upload (using the Frontend attachment field)

6. Can you use insert an image already in the media library without problems for methods 1 and 2?

7. Just in case it’s a WordPress problem try doing an upload from the backend admin Media Library page.

Hi prof,

OK, have worked through the list above.

I did 1 and 2 as instructed then tested in Firefox and Chrome (latest versions).

When trying to upload a featured image or attachment, I get the issues as previously reported – it uploads to 100% but then no thumbnail appears or attachment. Then, when submitting the form, both browsers now have ‘Please Wait’ just hanging and the Firefox Firebug console flags up an error which reads:

Load denied by X-Frame-Options: https://mysite/wp-admin/admin-ajax.php does not permit cross-origin framing.
and
Error: Permission denied to access property 'document'

The second error then points to line 11 in file jquery.form.min.js as the code error.

The Chrome browser throws up (on submit):

Refused to display 'https://mysite/wp-admin/admin-ajax.php' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.

As for the other bits, the inline editor won’t upload images and throws an error but you can select existing ones. The attachment and upload featured image as we have said don’t work properly either.

You can upload images in the wordpress media manager in the admin area however so it doesn’t seem to be a WP issue.

I have screen grabs of all the code errors but I wasn’t sure how to save log files from the console.

So, any thoughts?!

Oh, and despite the errors, it did seem that the posts were actually being created as they appeared on the site and in the admin section however with no images or attachments.

Having re-enabled the plugins, I go back to the error ‘cheating’. coming up on submit and no errors showing in the console (presumably because the form is never getting to ‘submit’).

Hi Jonga,

I have never seen this ‘X-Frame-Options’ error before. It may be related to using https so try it again with just http.

As to getting logs off Firebug the following two tools are what I use.

To enable the ability to save a ‘Net’ log install the following Firebug extension NetExport and restart Firefox

Using the ‘Export’ option on the ‘Net’ option in the Firebug bar save the log as a ‘HAR’ file.

To save the console log along in a similar manner use ConsoleExport.

Send both to me at abruinATihugDOTcomDOTau

I looked at little bit more into the X-Frame problem and found here it is a web server setting. This is what I think is causing your problems. One potential fix is here

Right,

I have had a break through.

I have not been using SSL on all the pages of the site other than for payment or sensitive data. Therefore the site has mainly been using http with https hyperlinks and overides for particular pages only.

Having set to use https on the WPUF add item page, this seems to have resolved the ‘cheating?’ issue and the fix in your post above seems to have resolved the X-Frame problem.

I need to spend a bit more time testing to ensure that the problem is resolved but we seem to have at least made a move in the right direction and hopefully this will be resolved.

Thanks for your help so far.

I will email you my two firebug exports – one with http and one without in case this helps with more specific debugging issues.

Thanks.

Thanks jonga. Could you post details of your fixes here in order to help other users who might experience the same problem.

Hi prof,

In terms of the X-Frame-Options error:

Load denied by X-Frame-Options: https://mysite/wp-admin/admin-ajax.php does not permit cross-origin framing.

which I was seeing in the Firebug console when trying to submit a post using WPUF, the fix was to add the following line to the file admin-ajax.php after the opening PHP tag:

header('X-Frame-Options: GOFORIT');

Then, to resolve the error where I was receiving a ‘Cheating?’ message when submitting (which was the next error after the fix above), I realised that my configuration was throwing an error due to me not using SSL on the submission page. I changed this so that the WPUF Add post and edit post pages now use SSL and this resolved the error.

The exact route cause of the second part I am unsure but I have sent you the console log for the non-http submission so if anything crops up please do let me know.

Hi Jonga,

You mention below of having to use SSL to solve the problem is not normal behaviour as Frontend generally works fine for http. This sounds like a server problem too. Could your please send me the logs with the ‘Cheating?’ message in it as well.

Then, to resolve the error where I was receiving a ‘Cheating?’ message when submitting (which was the next error after the fix above), I realised that my configuration was throwing an error due to me not using SSL on the submission page. I changed this so that the WPUF Add post and edit post pages now use SSL and this resolved the error.

I thought that was the log with the ‘cheating?’ message? was it not?

If not I may have to regenerate it.

I’m yet to look at the log but it seems I misunderstood your previous message.