<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tribulant Documentation &#187; Know Issues</title>
	<atom:link href="http://docs.tribulant.com/category/know-issues/feed" rel="self" type="application/rss+xml" />
	<link>http://docs.tribulant.com</link>
	<description>Documentation base for Tribulant software packages</description>
	<lastBuildDate>Fri, 07 Jun 2013 08:04:17 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>AJAX and Jquery Conflicts</title>
		<link>http://docs.tribulant.com/know-issues/6713</link>
		<comments>http://docs.tribulant.com/know-issues/6713#comments</comments>
		<pubDate>Thu, 02 Aug 2012 18:37:03 +0000</pubDate>
		<dc:creator>vitor</dc:creator>
				<category><![CDATA[Know Issues]]></category>

		<guid isPermaLink="false">http://docs.tribulant.com/?p=6713</guid>
		<description><![CDATA[With the increasing popularity of WordPress, many themes are being released daily. Unfortunately many of these themes are poorly coded and some others do not follow the WordPress coding standards. If you have been experiencing issues with Ajax calls and elements that make use of the jQuery Library after you...]]></description>
				<content:encoded><![CDATA[<p>With the increasing popularity of WordPress, many themes are being released daily. Unfortunately many of these themes are poorly coded and some others do not follow the WordPress coding standards.</p>
<p>If you have been experiencing issues with Ajax calls and elements that make use of the jQuery Library after you installed a WordPress Plugin, make sure you go through the list of possible causes below.</p>
<h3>Javascript files being inserted into your theme using the wrong method</h3>
<p>This is definitely the most common reason why your theme may be not working properly. Whenever a developer wants to add a new Javascript file to a theme or a plugin there is a simple rule that should be followed.</p>
<p>WordPress uses the <a href="http://codex.wordpress.org/Function_Reference/wp_enqueue_script" target="_blank">wp_enqueue_script</a> function to add Javascript files to your website. This method prevents your website from calling multiple instances of the same script and it also makes sure that your website is using the latest available version from that file. By using this simple method, your website is most likely to be free from Javascript errors and conflicts.</p>
<p>It is quite easy to identify a theme or a plugin that doesn`t use the <a href="http://codex.wordpress.org/Function_Reference/wp_enqueue_script" target="_blank">wp_enqueue_script</a> function. You can open your theme`s header.php and footer.php files, if you see something like this:</p>
<p><img class="alignnone" src="http://content.screencast.com/users/VitorArgos/folders/Jing/media/3c4db7e4-dae3-4a6b-b569-72ac34167962/2012-07-06_2356.png" alt="" width="511" height="153" /></p>
<p>It means that your theme is manually inserting the files on your website, in this case, if one of your plugins wants to use this same file it will insert a second instance of it, causing some of the features that use the script not to work properly.</p>
<h3>The Solution</h3>
<p>The easiest way to fix this issue is to remove the script from your theme header.php, by doing this, only the version being used by your plugin would be called on your website.</p>
<p>In case you are more familiar with programming languages you can try to insert the necessary Javascript files to your theme using the <a href="http://codex.wordpress.org/Function_Reference/wp_enqueue_script" target="_blank">wp_enqueue_script</a> function. You can see a complete tutorial on how to do that <a href="http://wp.tutsplus.com/tutorials/the-ins-and-outs-of-the-enqueue-script-for-wordpress-themes-and-plugins/" target="_blank">here</a></p>
<h3>jQuery not using compatibility mode</h3>
<p>jQuery is probably the most famous Javascript Library in the moment, as it is not exclusively used by WordPress, most tutorials and guides will use a code like this:</p>
<pre class="brush: xml; title: This is a code example only; notranslate">
/* How jQuery is taught on most tutorials */
$(&quot;#element_id&quot;).whatever();
</pre>
<p>But since WordPress has some other libraries that may be used by different themes and plugins, the use of $ may cause conflicts between these scripts. If you are familiar with Firebug or any other developer tool used to debug your code, you should probably be seeing the following error on your Console: &#8220;$ is not a function&#8221;</p>
<h3>The Solution</h3>
<p>In order to fix this issue, you can edit your Javascript files to make use of &#8220;jQuery&#8221; instead of &#8220;$&#8221;, so you would get something like this:</p>
<pre class="brush: xml; title: This is a code example only; notranslate">
/* How jQuery should be used on WordPress */
jQuery(&quot;#element_id&quot;).whatever();
</pre>
<h3>Theme making modifications in a shortcode output</h3>
<p>Some WordPress themes will disable the <a href="http://codex.wordpress.org/Function_Reference/wpautop" target="_blank">wpautop</a> function in order to fix and clean your content output. Unfortunately, this method will also change the external outputs, which sometimes, may break the javascript and/or other features that are directly included in the plugin shortcode. This can easily be avoided by putting the plugin shortcode between [raw] tags, so you would have something similar to this:</p>
<pre class="brush: xml; title: This is a code example only; notranslate">
[raw][shortcode_here][/raw]
</pre>
<p>The raw tag is usually added by the theme itself in order to solve this kind of issue, but if by any chance your theme doesn`t support it, you must get in contact with the theme creators and ask them about the function that is modifying your content output and how to disable it.</p>
<h2>Missing wp_header and/or wp_footer functions on theme</h2>
<p><a href="http://codex.wordpress.org/Plugin_API/Action_Reference/wp_head" target="_blank">wp_head</a> and <a href="http://codex.wordpress.org/Function_Reference/wp_footer" target="_blank">wp_footer</a> are vital functions to maintain your website working properly, specially when you have different plugins installed. Basically what these functions do is to indicate the path for the insertion of javascript files on your theme, if the plugin can`t find this path it won`t be able to call the necessary files on your website.</p>
<p>The Solution</p>
<p>Inside your theme header.php you must insert the following code right before the &lt;/head&gt; closing tag:</p>
<pre class="brush: xml; title: This is a code example only; notranslate">
&lt;!-- Here you should see a lot of tags and content --&gt;
...
...
&lt;!--?php wp_head(); ?--&gt;
</pre>
<p><!-- This is where you must insert the wp_head() function --><br />
<!--?php wp_head(); ?--><br />
Inside your theme footer.php you must insert the following code right at the bottom of the file:</p>
<pre class="brush: xml; title: This is a code example only; notranslate">
&lt;!--?php wp_footer(); ?--&gt;
</pre>
<p>You can see a detailed guide about both functions here: <a href="http://buckleupstudios.com/blog/wordpress-wp_head-wp_footer-functions/" target="_blank">www.buckleupstudios.com/blog/wordpress-wp_head-wp_footer-functions/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://docs.tribulant.com/know-issues/6713/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Black Label</title>
		<link>http://docs.tribulant.com/know-issues/6059</link>
		<comments>http://docs.tribulant.com/know-issues/6059#comments</comments>
		<pubDate>Fri, 20 Apr 2012 10:50:24 +0000</pubDate>
		<dc:creator>Antonie Potgieter</dc:creator>
				<category><![CDATA[Know Issues]]></category>
		<category><![CDATA[Black Label]]></category>
		<category><![CDATA[known issues]]></category>
		<category><![CDATA[Problematic Theme]]></category>
		<category><![CDATA[Themeforest]]></category>
		<category><![CDATA[WordPress Themes]]></category>

		<guid isPermaLink="false">http://docs.tribulant.com/?p=6059</guid>
		<description><![CDATA[The Black Label WordPress theme is a problematic theme as it doesn&#8217;t use WordPress conventions and doesn&#8217;t consider 3rd party plugins. We do not recommend using this theme. Theme Name: Black Label Theme Version: 1.5.0 The Problems 1. Enqueues it&#8217;s own jQuery version This is in the blacklabel/functions.php file 2....]]></description>
				<content:encoded><![CDATA[<small><a href="http://docs.tribulant.com/know-issues/4942" title="Conflicting Themes">&laquo; Conflicting Themes</a></small>
<p>The Black Label WordPress theme is a problematic theme as it doesn&#8217;t use WordPress conventions and doesn&#8217;t consider 3rd party plugins. We do not recommend using this theme.</p>
<p><strong>Theme Name:</strong> <a href="http://themeforest.net/item/black-label-fullscreen-video-image-background/336949?WT.ac=portfolio_thumb&amp;WT.seg_1=portfolio_thumb&amp;WT.z_author=eneaa" rel="nofollow" target="_blank">Black Label<br />
</a><strong>Theme Version:</strong> 1.5.0</p>
<h2>The Problems</h2>
<h3>1. Enqueues it&#8217;s own jQuery version</h3>
<p>This is in the blacklabel/functions.php file</p>
<h3>2. Doesn&#8217;t enqueue scripts in general</h3>
<p>This is throughout the theme, mainly in the blacklabel/header.php, blacklabel/theme_scripts/scripts.php and blacklabel/footer.php files.</p>
<h3>3. Uses jQuery object before wp_head has executed</h3>
<p>This is in the blacklabel/theme_scripts/scripts.php file.</p>
<h3>4. Removes the_content filters</h3>
<p>Removes the default the_content filters and applies it&#8217;s own. In the blacklabel/framework/shortcodes/columns.php file of the theme.</p>
]]></content:encoded>
			<wfw:commentRss>http://docs.tribulant.com/know-issues/6059/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WP-Genius</title>
		<link>http://docs.tribulant.com/know-issues/6029</link>
		<comments>http://docs.tribulant.com/know-issues/6029#comments</comments>
		<pubDate>Thu, 12 Apr 2012 10:22:04 +0000</pubDate>
		<dc:creator>Antonie Potgieter</dc:creator>
				<category><![CDATA[Know Issues]]></category>
		<category><![CDATA[known issues]]></category>
		<category><![CDATA[Premium WordPress plugins]]></category>
		<category><![CDATA[Problematic Theme]]></category>
		<category><![CDATA[Solostream]]></category>
		<category><![CDATA[Tribulant Software]]></category>
		<category><![CDATA[WordPress Themes]]></category>
		<category><![CDATA[WP-Genius]]></category>

		<guid isPermaLink="false">http://docs.tribulant.com/?p=6029</guid>
		<description><![CDATA[Theme Name: WP-Genius Theme Version: 1.0 Summary: Doesn&#8217;t use WordPress conventions. The Problems 1. Doesn&#8217;t enqueue scripts The WP-Genius theme doesn&#8217;t enqueue Javascript scripts using the wp_enqueue_script function. The theme simply injects SCRIPT tags into the head of the WordPress site. These scripts are placed in the header.php file of...]]></description>
				<content:encoded><![CDATA[<small><a href="http://docs.tribulant.com/know-issues/4942" title="Conflicting Themes">&laquo; Conflicting Themes</a></small>
<p><strong>Theme Name:</strong> <a title="WP-Genius" href="http://www.solostream.com/wordpress-themes/wp-genius/" rel="nofollow" target="_blank">WP-Genius</a><br />
<strong>Theme Version:</strong> 1.0<br />
<strong>Summary:</strong> Doesn&#8217;t use WordPress conventions.</p>
<h2>The Problems</h2>
<h3>1. Doesn&#8217;t enqueue scripts</h3>
<p>The WP-Genius theme doesn&#8217;t enqueue Javascript scripts using the <code>wp_enqueue_script</code> function. The theme simply injects <code>SCRIPT</code> tags into the head of the WordPress site. These scripts are placed in the <code>header.php</code> file of the theme.</p>
<h3>2. Uses a custom version of jQuery</h3>
<p>The theme doesn&#8217;t use the jQuery script distributed with WordPress and simply includes it&#8217;s own, custom jQuery version which is not appropriate. This is in the <code>header.php</code> file of the theme.</p>
<h3>3. Doesn&#8217;t use the jQuery object</h3>
<p>The theme uses the jQuery dollar ($) object instead of the correct <code>jQuery</code> object. This is in the <code>header.php</code> file of the theme and also in the <code>js/slideshow.js</code> file of the theme.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://docs.tribulant.com/know-issues/6029/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress.com Stats</title>
		<link>http://docs.tribulant.com/know-issues/6027</link>
		<comments>http://docs.tribulant.com/know-issues/6027#comments</comments>
		<pubDate>Wed, 11 Apr 2012 10:06:42 +0000</pubDate>
		<dc:creator>Antonie Potgieter</dc:creator>
				<category><![CDATA[Know Issues]]></category>
		<category><![CDATA[Conflict]]></category>
		<category><![CDATA[Jetpack]]></category>
		<category><![CDATA[Known issue]]></category>
		<category><![CDATA[newsletter plugin]]></category>
		<category><![CDATA[Newsletter Post Content]]></category>
		<category><![CDATA[Post Content Not Included]]></category>
		<category><![CDATA[Premium WordPress plugins]]></category>
		<category><![CDATA[Problematic plugin]]></category>
		<category><![CDATA[Send as Newsletter]]></category>
		<category><![CDATA[Send as Newsletter content empty]]></category>
		<category><![CDATA[Tribulant Software]]></category>
		<category><![CDATA[WordPress.com Stats]]></category>

		<guid isPermaLink="false">http://docs.tribulant.com/?p=6027</guid>
		<description><![CDATA[Plugin Name: WordPress.com Stats Plugin Version: 1.8.5 Plugins Affected: Possibly all plugins Summary: Steals post content on save_post hook. The Problem The WordPress.com Stats plugin steals the posted post content on the save_post hook when the post is published or updated. It could be outdated and incompatible with the latest...]]></description>
				<content:encoded><![CDATA[<small><a href="http://docs.tribulant.com/know-issues/4949" title="Conflicting Plugins">&laquo; Conflicting Plugins</a></small>
<p><strong>Plugin Name:</strong> <a title="WordPress.com Stats" href="http://wordpress.org/extend/plugins/stats/" rel="nofollow" target="_blank">WordPress.com Stats</a><br />
<strong>Plugin Version:</strong> 1.8.5<br />
<strong>Plugins Affected:</strong> Possibly all plugins<br />
<strong>Summary:</strong> Steals post content on save_post hook.</p>
<h3>The Problem</h3>
<p>The <a title="WordPress.com Stats" href="http://wordpress.org/extend/plugins/stats/" rel="nofollow" target="_blank">WordPress.com Stats plugin</a> steals the posted post content on the save_post hook when the post is published or updated. It could be outdated and incompatible with the latest WordPress.</p>
<h3>The Solution</h3>
<p>The WordPress.com Stats plugin has been replaced by the <a title="Jetpack by WordPress.com" href="http://wordpress.org/extend/plugins/jetpack/" rel="nofollow" target="_blank">Jetpack plugin</a>. Install, connect and configure the <a title="Jetpack by WordPress.com" href="http://wordpress.org/extend/plugins/jetpack/" rel="nofollow" target="_blank">Jetpack plugin</a> for stats in your WordPress.</p>
]]></content:encoded>
			<wfw:commentRss>http://docs.tribulant.com/know-issues/6027/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WP-reCAPTCHA</title>
		<link>http://docs.tribulant.com/know-issues/5968</link>
		<comments>http://docs.tribulant.com/know-issues/5968#comments</comments>
		<pubDate>Mon, 02 Apr 2012 11:27:43 +0000</pubDate>
		<dc:creator>Antonie Potgieter</dc:creator>
				<category><![CDATA[Know Issues]]></category>
		<category><![CDATA[Known issue]]></category>
		<category><![CDATA[Premium WordPress plugins]]></category>
		<category><![CDATA[Problematic plugin]]></category>
		<category><![CDATA[ReCaptcha]]></category>
		<category><![CDATA[shopping cart]]></category>
		<category><![CDATA[Tribulant Software]]></category>
		<category><![CDATA[WordPress ECommerce]]></category>
		<category><![CDATA[WordPress Shopping Cart Plugin]]></category>
		<category><![CDATA[wp ecommerce]]></category>
		<category><![CDATA[WP-reCAPTCHA]]></category>

		<guid isPermaLink="false">http://docs.tribulant.com/?p=5968</guid>
		<description><![CDATA[The WordPress WP-reCAPTCHA plugin is a known, problematic plugin. Plugin Name: WP-reCAPTCHA. Plugins Affected: WordPress Shopping Cart plugin. Summary: Replaces all emails in content with an anti-spam link. The Problem The WP-reCAPTCHA plugin replaces all emails inside the content of posts/pages with an anti-spam link to reveal the email address...]]></description>
				<content:encoded><![CDATA[<small><a href="http://docs.tribulant.com/know-issues/4949" title="Conflicting Plugins">&laquo; Conflicting Plugins</a></small>
<p>The <a href="http://wordpress.org/extend/plugins/wp-recaptcha/" rel="nofollow" target="_blank">WordPress WP-reCAPTCHA plugin</a> is a known, problematic plugin.</p>
<p><strong>Plugin Name:</strong> <a title="WP-reCAPTCHA" href="http://wordpress.org/extend/plugins/wp-recaptcha/" rel="nofollow" target="_blank">WP-reCAPTCHA</a>.<br />
<strong>Plugins Affected:</strong> <a title="WordPress Shopping Cart" href="http://tribulant.com/plugins/view/10/wordpress-shopping-cart-plugin">WordPress Shopping Cart plugin</a>.<br />
<strong>Summary:</strong> Replaces all emails in content with an anti-spam link.</p>
<h2>The Problem</h2>
<p>The WP-reCAPTCHA plugin replaces all emails inside the content of posts/pages with an anti-spam link to reveal the email address with a verification process.</p>
<p>As a result, it breaks certain parts of the WordPress Shopping Cart plugin such as payment forms, account pages, etc.</p>
<p><a class="colorbox" title="WP-reCAPTCHA issue" href="http://docs.tribulant.com/wp-content/uploads/WP-reCaptcha-issue.png"><img class="alignnone size-large wp-image-5969" style="border-style: initial; border-color: initial; border-width: 0px; margin: 0px;" title="WP-reCaptcha issue" src="http://docs.tribulant.com/wp-content/uploads/WP-reCaptcha-issue-620x317.png" alt="" width="620" height="317" /></a></p>
<h2>The Solution</h2>
<p>You can turn off MailHide for posts and pages in the WP-reCAPTCHA settings by unticking/unchecking the &#8220;<strong>Posts and Pages</strong>&#8221; checkbox as shown below.</p>
<p><a class="colorbox" title="Turn off mail hide for posts/pages" href="http://docs.tribulant.com/wp-content/uploads/MailHide.png"><img class="alignnone size-large wp-image-5971" style="border-style: initial; border-color: initial; border-width: 0px; margin: 0px;" title="MailHide" src="http://docs.tribulant.com/wp-content/uploads/MailHide-620x393.png" alt="" width="620" height="393" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://docs.tribulant.com/know-issues/5968/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
