Problem Displaying The ShortCode Form Within Post/Page Editor

[yasserb]

Hello,

I am using the Newline Theme from damojothemes.com [http://newline.damojothemes.com/] and WordPress 3.4.2 and eStore v. v6.9.1

The issue is that after installing the plugin and adding a test product without problem, I went to a new post and after clicking the Shopping Cart Icon withing the Post editor, the pop up box just displayed a small iframe from the home page. After it I tried the same from a page and I got the same result.

However if I add the code [wp_eStore_buy_now:product_id:1:end] manually, everything works Ok.

I would appreciate any help with this issue. Thanks

[Peter]

Hi,

This sounds like an issue with your theme which is conflicting with the eStore popup window.

To verify this you can try the theme conflict test and revert to a properly coded theme such as twentyeleven.

https://support.tipsandtricks-hq.com/forums/topic/test-to-identy-a-conflicting-theme-or-plugin

[yasserb]

After checking my theme with WP Theme Check this was the result. I am not a php savy so I would appreciate if you could tell me what to tell to the theme developers they should fix so the WP eStore works properly thanks…

Running 18487 tests against Newline Premium Business WordPress Theme using Guidelines Version: 20120823 Plugin revision:

One or more errors were found for Newline Premium Business WordPress Theme.

WARNING: Found base64_decode in the file option-tree/classes/class.admin.php. base64_decode() is not allowed.

Line 257: $new_options = unserialize( base64_decode( $rawdata ) );

Line 271: $new_layouts = unserialize( base64_decode( $rawdata ) );

Line 1129: $new_options = unserialize( base64_decode( $string ) );

Line 1336: $new_options = unserialize( base64_decode( $options_layouts[$id] ) );

Line 1397: $new_options = unserialize( base64_decode( $string ) );

WARNING: Found base64_decode in the file functions/thumb.php. base64_decode() is not allowed.

Line 221: $imgData =

WARNING: Both DOS and UNIX style line endings were found in the file functions/cache/timthumb_int_1c4a7f003d29f22d03bb51b50aff0135.timthumb.txt. This causes a problem with SVN repositories and must be corrected before the theme can be accepted. Please change the file to use only one style of line endings.

WARNING: readfile was found in the file functions/thumb.php possible file operations.

Line 1226: $bytes = @readfile($file);

WARNING: fwrite was found in the file option-tree/functions/functions.php possible file operations.

Line 348: fwrite( $f, ‘{$markerline}n’ );

Line 350: fwrite( $f, ‘{$markerline}’ );

Line 354: fwrite( $f, ‘/* BEGIN {$marker} */n’ );

Line 355: fwrite( $f, ‘{$insertion}n’ );

Line 356: fwrite( $f, ‘/* END {$marker} */n’ );

Line 364: fwrite( $f, ‘nn/* BEGIN {$marker} */n’ );

Line 365: fwrite( $f, ‘{$insertion}n’ );

Line 366: fwrite( $f, ‘/* END {$marker} */n’ );

WARNING: fwrite was found in the file functions/thumb.php possible file operations.

Line 1006: fwrite(self::$curlFH, $d);

WARNING: fread was found in the file functions/thumb.php possible file operations.

Line 1023: $imgType = fread($fp, 3);

WARNING: fopen was found in the file option-tree/functions/functions.php possible file operations.

Line 332: if ( !$f = @fopen( $filepath, ‘w’ ) )

WARNING: fopen was found in the file functions/thumb.php possible file operations.

Line 796: $fp = fopen($tempfile,’r’,0,$context);

Line 803: $fh = fopen($lockFile, ‘w’);

Line 1020: $fp = fopen($this->cachefile, ‘rb’);

Line 1163: self::$curlFH = fopen($tempfile, ‘w’);

WARNING: file_put_contents was found in the file functions/thumb.php possible file operations.

[redacted the rest of the errors]

[Peter]

Thanks for the info. However, you need to send this info to your theme developer (not us). Your theme developer is responsible for giving you a properly coded theme.

I have a feeling that the problem is caused by a javascript conflict of some kind due to your incorrectly coded theme.

I recommend doing the following:

– log into your WP admin panel using the Chrome browser.

– Then go to the post editor.

– anywhere within the post editor screen, right click and select “Inspect element” (this will launch Chrome developer tools)

– then look at the very bottom right hand side of the screen (near the settings wheel).

If there is a javascript issue you should see a little red ‘x’.

– If you see the little red ‘x’, click on it to see more information about the issue.

You should be able to see which javascript file has an error.

Then you can copy this info and send it to the designers and post it here if you want us to verify the information for you.

[Author]

Posts