Cheatin uh? (When trying to upload media via 3rd party theme)

Thanks @ kevinslane for really quick work and fast response.
I will download and replace the file.
Once after checking the upload logo, favicon, media i will let you know whether it is working or not.
Thanks a lot

@ kevinslane
Unfortunately that change didn’t work for me at all.
One change that is working is change in line 126 from the core file that is being discussed. But that too is temporary solution and vulnerable to security as suggested by wordpress community too.
Can you please help me out and let me know other possibility so that i can get rid of that message.

Regards

Many thanks to you @kevinslane. Fixing the post_id to post_ID in my themes works great, without having to touch core.

For anyone using Elegant themes…go to themename>epanel>js>custom_uploader

and change all occurences of post_id to post_ID. Worked great for me. I recommend you edit through 7-zip or similar, when i rezipped the theme and uploaded, i began getting a missing css file error.

Hey, don’t spread wrong information. As I said before, replacing post_id with post_ID is a wrong solution even if it seems to work fine at a glance. If you think it’s right, you should show us the source about post_ID parameter.

This issue is caused by changeset 21048. So correct solution is removing added (green) lines in “wp-admin/media-upload.php”, or using post_id=0. You should not use post_ID since it does not exist in WordPress.

I deleted a picture from media that had been uploaded to the front page under “custom logo”. I relized this error and went to the place in the striking under custom logo and tried to add a new picture and get the error Cheatin eh? I need this fixed ASAP…it’s the logo on the front of our website and it looks terrible.
[Contact details retracted by moderator]

I have another theory after realizing that my admin user does not have the problem but another user with different privileges was having the problem.

Most of the images and other changes that were previously successfully submitted were performed by the admin. But more recently I was using a different user with less privileges.

I have the plug-in User Role Editor installed, and the user that was having the problem has a role based on Editor, but did not have the permission Manage Options checked.

I tested by using two different computers to test: 1) one logged in as Administrator role to change permissions, 2) another logged in with Editor role to submit changes. I have able to successfully create or fix the problem by simply unchecking or checking the Manage Options permission in the User Role Editor.

So at least my version of the problem can be fixed by checking the Manage Options permission for the role where you are having the problem.

I am using: WP 3.5.1 User Role Editor 3.10 (and some other plug-ins).

I would be interested in your thoughts on the above observations, and whether adding the above User Role Editor plug-in, and manipulating the Manage Options permission is the real cause/fix.

Thanks Mr.producerism……