WPML 3.1.8.x and the double slash problems continues.
Well, after my previous post WPML have relised a new version 3.1.8.2, but it looks like this error gone unnoticed.
One other error with my solution was that on the homepage paging it had errors, so here is the revised version of the fix for WPML.
$arrUrl = parse_url($absolute_home_url);
if(!isset($arrUrl[‘path’])) $arrUrl[‘path’] = ‘/’;
$absolute_home_url = $arrUrl[‘scheme’].”://”.$arrUrl[‘host’].$arrUrl[‘path’];
if(isset($arrUrl[‘query’])) $absolute_home_url .= ‘?’.$arrUrl[‘query’];
if(isset($arrUrl[‘fragment’])) $absolute_home_url .= ‘#’.$arrUrl[‘fragment’];
unset($arrUrl);
$arrUrl = parse_url($this->settings[ ‘language_domains’ ][ $code ]);
if(!isset($arrUrl[‘path’])) $arrUrl[‘path’] = ‘/’;
$this->settings[ ‘language_domains’ ][ $code ] = $arrUrl[‘scheme’].”://”.$arrUrl[‘host’].$arrUrl[‘path’];
if(isset($arrUrl[‘query’])) $this->settings[ ‘language_domains’ ][ $code ] .= ‘?’.$arrUrl[‘query’];
if(isset($arrUrl[‘fragment’])) $this->settings[ ‘language_domains’ ][ $code ] .= ‘#’.$arrUrl[‘fragment’];
unset($arrUrl);
$arrUrl = parse_url($new_url);
if (!empty($arrUrl)){
if(!isset($arrUrl[‘path’])) $arrUrl[‘path’] = ‘/’;
$new_url = $arrUrl[‘scheme’].”://”.$arrUrl[‘host’].$arrUrl[‘path’];
if(isset($arrUrl[‘query’])) $new_url .= ‘?’.$arrUrl[‘query’];
if(isset($arrUrl[‘fragment’])) $new_url .= ‘#’.$arrUrl[‘fragment’];
}
unset($arrUrl);
The fix goes into sitepress.class.php on between lines 6463 and 6464:
$this->settings[ ‘language_domains’ ][ $default_language ] = $wpdb->get_var( “SELECT option_value FROM $wpdb->options WHERE option_name = ‘siteurl'”);
$new_url = str_replace( $absolute_home_url, $this->settings[ ‘language_domains’ ][ $code ], $new_url );
WPML makes the user logged out on 3.1.8.1 upgrade
WPML rolled out an update to their plugin version 3.1.8.1.
But since the update you cannot work in the admin panel any more, each url will have more then one slash in it.
Here is my fix for the problem (until thy will issue an update).
The problem is in the sitepress.class.php file on line 6464, and created by in the addition of line 6463.
In line 6463 they have added a selection of site_url paramtere from the global parameter set of wordpress:
$this->settings[ ‘language_domains’ ][ $default_language ] = $wpdb->get_var( “SELECT option_value FROM $wpdb->options WHERE option_name = ‘siteurl'”);
This selection have an url of the website WITH the trailing slash in it.
And this data is sent to the next line: 6464
$new_url = str_replace( $absolute_home_url, $this->settings[ ‘language_domains’ ][ $code ], $new_url );
What this creates is a URL with next features:http://localhost//wp-admin/?lang=frAnd the double slash created the logout problem.By addint my lines of code, the error can be managed, untill a more permanent fix will be applied by WPML team:Simple add next code between 6463 and 6464 (inclusive)
$this->settings[ ‘language_domains’ ][ $default_language ] = $wpdb->get_var( “SELECT option_value FROM $wpdb->options WHERE option_name = ‘siteurl'”);
$arrUrl = parse_url($absolute_home_url);
if(!isset($arrUrl[‘path’])) $arrUrl[‘path’] = ‘/’;
$absolute_home_url = $arrUrl[‘scheme’].”://”.$arrUrl[‘host’].$arrUrl[‘path’];
if(!isset($arrUrl[‘query’])) $absolute_home_url .= ‘?’.$arrUrl[‘query’];
if(!isset($arrUrl[‘fragment’])) $absolute_home_url .= ‘#’.$arrUrl[‘fragment’];$arrUrl = parse_url($this->settings[ ‘language_domains’ ][ $code ]);
if(!isset($arrUrl[‘path’])) $arrUrl[‘path’] = ‘/’;
$this->settings[ ‘language_domains’ ][ $code ] = $arrUrl[‘scheme’].”://”.$arrUrl[‘host’].$arrUrl[‘path’];
if(!isset($arrUrl[‘query’])) $this->settings[ ‘language_domains’ ][ $code ] .= ‘?’.$arrUrl[‘query’];
if(!isset($arrUrl[‘fragment’])) $this->settings[ ‘language_domains’ ][ $code ] .= ‘#’.$arrUrl[‘fragment’];$new_url = str_replace( $absolute_home_url, $this->settings[ ‘language_domains’ ][ $code ], $new_url );
WordPress gone Green – 3.4 is out!
The latest point release of WordPress was just launched to the masses a few hours ago.
We’re most excited about all the nifty new theme customization tools.
How to fix Zend Server on Ubuntu 12.04 Precise
After a long battle a solution is here!
Many thanks to Alex Sherman @AlxShr from BelleRon Technologies – www.belleron.com.
Disclaimer: Use at your own risk! Worked on clean 12.04 install.
First of all we used a script taken from: http://ubuntuforums.org/showthread.php?t=636724&page=2
#!/bin/bash #modded by japzone if [[ -z "$1" ]]; then echo "Syntax: $0 debfile" exit 1 fi DEBFILE="$1" TMPDIR=`mktemp -d /tmp/deb.XXXXXXXXXX` || exit 1 OUTPUT=`basename "$DEBFILE" .deb`.modfied.deb if [[ -e "$OUTPUT" ]]; then echo "$OUTPUT exists." rm -r "$TMPDIR" exit 1 fi dpkg-deb -x "$DEBFILE" "$TMPDIR" dpkg-deb --control "$DEBFILE" "$TMPDIR"/DEBIAN if [[ ! -e "$TMPDIR"/DEBIAN/control ]]; then echo DEBIAN/control not found. rm -r "$TMPDIR" exit 1 fi CONTROL="$TMPDIR"/DEBIAN/control MOD=`stat -c "%y" "$CONTROL"` gedit "$CONTROL" read -p "Press any key once you've finished editing and saved" if [[ "$MOD" == `stat -c "%y" "$CONTROL"` ]]; then echo Not modfied. else echo Building new deb... dpkg -b "$TMPDIR" "$OUTPUT" fi rm -r "$TMPDIR"
The script above saved as debedit.sh and given execute permissions by
chmod u+x debedit.sh
Packages downloaded by:
apt-get download libpq4 php-5.3-imap-zend-server
Then edited dependencies by:
./debedit.sh libpq4_8.1.17-0etch1_amd64.deb ./debedit.sh php-5.3-imap-zend-server_5.3.9+b260_amd64.deb
In the “Depends” line of each of them changed libkrb53 to libkrb5-3
After that installed each of the modified packages:
dpkg -i libpq4_8.1.17-0etch1_amd64.modfied.deb dpkg -i php-5.3-imap-zend-server_5.3.9+b260_amd64.modfied.deb
And then, finally, installed the zend server by:
apt-get install zend-server-ce-php-5.3
WOW! It Works!!!
This is continued from: Zend Server broken on Ubuntu 12.04
Thanks to the investment from Tesserent Limited we were able to create this script without a problem.
Visit or contact the tax office to know about our packages.
Zend Server on Ubuntu 12.04 Precise – @Zend responded “NO ETA”
I have contacted Zend founder Zeev and a friend of mine who have 2 servers running Zend Server Enterprise contacted Zend support.
The official response right now it: There is no ETA but because of the big interest we are looking at it.
I have checked the fix provided on Zend Forums (link) and using it it works, but you can not use imap any more, so if you have an applicaiton that uses it, dont install it.
But what I did found interesting is that the problem only occurs when you re enable Zend repositories after the upgrade, so if you made the upgrade to Ubuntu Precise with Zend Server installed you can continue to use it, just leave the repositories off.
In any case my advice is NOT to update to the new Ubuntu untill this is sorted out or to switch to a different LAMP stack.
A hack to temporary fix Zend Server on Ubuntu 12.04
User brinleyang on Zend forums has posted a temporary fix for the bug Zend introduced in their server on Ubuntu 12.04.
What he did is he created a quick hack and removed the dependency on libkrb in libpq and php-5.3-imap-zend-server deb packages and manually installed the packages after which installing zend server ce should work.
However, this will most likely break postgres and imap zend modules so it may not be the solution for people who require those modules.
You can follow the post here:
http://forums.zend.com/viewtopic.php?f=44&t=49693&hilit=ubuntu+12.04&sid=2435e3c7c2ebea1d4e4f3342f4148753&start=10
Zend Server broken on Ubuntu 12.04
To all of us using Zend Server on Ubuntu DONT update to the latest version 12.04 (at least until they will fix it!).
As of now, although they have this posted as a bug from January it’s impossible to use Zend Server 5.6 on Ubuntu 12.04 LTS.
The following packages have unmet dependencies:
zend-server-php-5.3 : Depends: php-5.3-common-extensions-zend-server but it is not going to be installed
The problem is seams is in libkrb53 which was a dummy for libkrb5-3 in previous versions and is no longer supported.
There is no known overrides as of now.
Another Week another beta – WordPress 3.4 Beta 2
Well the second beta is out, and about 60 bug fixes were commited …
We will see how it works 🙂
WordPress 3.4 Beta 1 – Developer preview
WordPress developer team have released Beta 1 of the next version of WordPress.
This is not a production release, only install it on test servers to check on your themes and plugins!
If all goes well, WordPress 3.4 will be released in May. If you want to be a beta tester, you should check out the Codex article on how to report bugs.
Here’s some of what’s new:
- Theme Customizer with Previewer
- Flexible Custom Header Sizes
- Selecting Custom Header and Background Images from Media Library
- Better experience searching for and choosing a theme
And some of the under-the-hood changes:
- New XML-RPC API for external and mobile applications
- New API for registering theme support for custom headers and backgrounds
- Performance improvements to WP_Query by splitting the query (Please test!)
- Internationalization improvements (improved performance and locale support)
- Performance and API improvements when working with lists of installed themes
- Support for installing child themes from the WordPress Themes Directory
Remember, if you find something you think is a bug, report it! You can bring it up in the alpha/beta forum, you can email it to the wp-testers list, or if you’ve confirmed that other people are experiencing the same bug, you can report it on the WordPress Core Trac. (We recommend starting in the forum or on the mailing list.)
WPMU Ultimate Facebook Addon plugin Upgraded to version 0.3
Well as stated in the topic, I have updated the WPMU Ultimate Facebook plugin Fix to version 0.3.
This is a maintenance only version since it’s only fixing posting description with a quotes (single quote to be exact).
You can download the plugin from: http://wordpress.org/extend/plugins/wpmu-dev-facebook-addon/
And you can get the plugin from: WPMUDev.org