Daniel Craig Jallits

Had the same or similar issue with v1.1.2 downloaded from the Plugin Directory and the plugin complained about the length of a few values being stored in Transient. DB collated with utf8_unicode_ci

Dumped the manually downloaded plugin and used https://github.com/Automattic/developer as a submodule.

Frederick,

Is there a new ETA on the release yet? Anxiously awaiting this one like everyone else!

Thanks Alex! Another fine plugin from a trusted source.

For anyone else who may come across this. The double quotes need to be escaped in the first and last echo statements. So the code would be as follows:

<?php
	if ( function_exists( 'get_option_tree') )
	{
		echo "<img src=\"";
		echo get_option_tree( 'lbbc_sermon_series_picture' );
		echo "\" />";
	}
?>

Please see my comments under Plugins & Hack support for the plugin: WordPress SEO by Yoast

Withdraw my comment.

I authenticated my domain, not by using the plug-in’s settings, but by manually inputting the URL in a new browser window.

I do recommend users read this thread…
https://groups.google.com/group/Google-Accounts-API/browse_thread/thread/84556800fcc0cf55/5c274154d6ba6e38

What did you do to generate there Warnings?

If you are running the latest version of WordPress and plug-ins that are compatible you will not have this issue. If the problem still persists then you need to deactivate all your plug-ins. Reactivate them one at a time until you figure out which are the culprits and inform the plug-in developer.

Quick ammendment to the post for users on Media Temple’s DV servers. There is a risk to this technique as this kills safe_mode for the site..

WP-CONFIG should contain the following:

define('FS_CHMOD_FILE', 0755);
define('FS_CHMOD_DIR', 0755);
define('FS_METHOD', 'ftpext');
define('FTP_BASE', '/httpdocs/');
define('FTP_CONTENT_DIR', '/httpdocs/wp-content/');
define('FTP_PLUGIN_DIR ', '/httpdocs/wp-content/plugins/');
define('FTP_USER', 'USERNAME');
define('FTP_PASS', 'PASSWORD');
define('FTP_HOST', 'SERVER:PORT');

HTACCESS should contain the following:
php_value safe_mode "1"

Just wanted to share real quick that this issue also is present in SVN managed installs. A quick switch from tags/2.8/ to /trunk/ does NOT resolve this issue either, just in case anyone in a similar setup was thinking of trying.

Does anyone else have the following declaration in their WP-CONFIG.PHP file? I am not sure if this is related to the SegFault, but I am definitely getting strange behavior when I set it to either TRUE or FALSE. Right now I have it commented out.

define('SAVEQUERIES', true);

https://www.yoursite.com/* has nothing to do with the WordPress side of things. The asterisk (*) is a wildcard, telling Google that anything in the domain is searchable.

So if I wanted to limit search results just to my blog, and the permalink for my blog is /blog. I would then enter https://www.yoursite.com/blog/*

Just a quick update… This situation resolved itself after 3 hours of me trying to fix it. I will say this, the above article at SugarCRM was of no help, I was in the process of triple-checking my settings in wp-config. I also was looking into my DNS settings.

All I know is that there has to be something to this, as this was my third domain on this box to do this over the past week and a half.

This is becoming a routine issue with a few of my domains as well. Anybody got the goods on the fix (aka resolution)?

WordPress/2.7
Apache/2.2.3
PHP/5.2.6
CentOS/5

The Prototype library was added to WordPress first, so the ‘$’ is set aside for all Prototype functionality. WordPress makes the coder use ‘jQuery’ in place of ‘$’. Therefore the first few lines of code should appear as:

<script type=”text/javascript”>
jQuery(document).ready(function() {
jQuery(‘.5radius’).corner({
…..
</script>
<script type=”text/javascript”>
jQuery(document).ready(function() {
jQuery(‘.sidebarbox’).corner({
…..
</script>