Comments 34

I could reproduce this error on my system.
The reason seems to be that the code for the replacement does not transform the slashes "/" in the text to search for into "secure" letters for a replacement pattern (the slash is one of the meta characters for the function preg_replace).

Basically that has to be fixed in the code of the plugin.

Workaround: you can put an "\" in front of every "/" in the search text (field "Find this text"). E.g.: "http:\/\/wordpress.org\/plugins\/" (instead of "http://wordpress.org/plugins/").Caveat: As soon as the plugin is fixed by the developer you have to remove the backslashes "\" from your search texts, otherwise your texts will not be found any more ...

This plugin was never intended to be used to change URL's nor does it indicate that it will do so anywhere - it is designed to change text as the description implies Network Wide Text Change.

However, as Emanaku has kindly pointed out that possibly with a bit of a coding change it can indeed be made to also successfully address URL's and this is what I am going to run by the lead developer of Ultimate Branding for his input on the likelihood of this happening.

Though this may take a bit longer then a normal ticket, I will try to get his invaluable insight and comment in here asap.

If you are still having an issue please let us know so that we may try to get you fixed up as soon as possible by choosing to check mark this ticket as unresolved below and posting any new errors or symptoms you are noticing.

This action will also bring your ticket up front back in plain view again within the ticket system.

I asked if the workaround mentioned in this thread had worked for anyone - I'd still like to know...
Do you know if it does?

If the plugin replaces text - it should work with links as they are made of text (the "T" in HTML). A URL looks different because of how the browser renders it - but it's just plain text being sent over the interwebs...

Let me rephrase the problem...

The issue is that the plugin crashes when you try to replace the character "/".

You are missing the point that this is not it's intended use, therefore it is not broken.

Taken directly from the Ultimate Branding plugin's page:“Network Wide Text Change” is basically “search and replace” for the backend of your WordPress site. Automatically change the word “WordPress” to the name of your business – everywhere.

Make note that the URL does not appear anywhere in this description, it clearly says Automatically change the word and obviously a URL is not a word.

Of course URL changing can certainly be submitted as a feature request.

Please advise where this is indicated as intended use, changing a URL, and I will certainly concede my position with apologies for being incorrect.

The 1.1 release is a fixed version of the old 1.0.5 release with the aim of fixing the issue that made us have to revert back to version 1.0.3. Now that it is out and there are no reports of the same issue we can move forward and get other bug fixes in the next few updates.

@Barry thank you for the update Chief but even afterwards when I enable Ultimate Branding 1.1 I still get a mass of issues, certainly due to the "/" still being in the database somewhere. Error screen shot below.

@Sándor Happy to see that you have managed to get this resolved with the latest update and thank you for being a WPMU DEV Community Member!

The 1.1 release is a fixed version of the old 1.0.5 release with the aim of fixing the issue that made us have to revert back to version 1.0.3. Now that it is out and there are no reports of the same issue we can move forward and get other bug fixes in the next few updates.

Can you please advise sir where to find the entry I made in the database?

I cannot figure out where it is storing the info i.e. "/"

I only inserted this to try to help another member confirming the issue and now I cannot use the plugin at all on my test installation. Of course I can always do a complete re-install - but that would take hours.

1.1.1 isn't working for me, even after deleting tables in phpadmin mentioned above. 1.0.3 does work (after I delete tables), so I'd recommend reverting back to that until all this is straightened out. I use the / key for making replaced text italic or bold, as well as for creating links, so its a big deal to have lost that branding functionality in the recent updates. Thanks for all the work you guys do.

o.k., that's how I read it. They are recreated when you reinstall the plugin. So, when 1.1.1 was reinstalled, the tables were recreated, but so was the bug. Deleted the tables again, reinstalled 1.0.3, tables recreated by the install, no bug.

Can you write *exactly* what you are putting in each box on the form to cause the error, because I've tried a lot of test strings and can't duplicate it now.

They are recreated when you reinstall the plugin. So, when 1.1.1 was reinstalled, the tables were recreated, but so was the bug.

Can you we be clear here - you mean options or records, not tables yes?

Can you do the following then -
In phpmyadmin open the wp_sitemeta table and find the records with a meta_key starting with translation_ and delete them (the records *not* the table).
Then open the wp_options table and find the records with an option_name starting with translation_ and delete them as well (again the records *not* the table).

Records, not tables, sorry for the confusion. (One of the records deleted is called the translation_table, but still my technical error). I deleted the records and reinstalled 1.1.2, again, and get the error again whenever I use the / character. Installing 1.0.3 does not produce the error.

Specifically and </b>, when used creating a link or bold text in the replacement text field, I get <\/a> and <\/b> displayed in the output. See attached.

How do you rate me?

Thank you for rating your experience!

We’re thrilled to hear you had a great experience with . Would you like to leave a comment about your experience?
Thanks for voting on your experience with , we’d love to get some feedback please.
Ohh no! We’re really sorry to hear you didn’t have a pleasant experience with , we’re always looking at how we can improve and would appreciate you provide some further feedback here please.
Type your feedback here

it's great that you had a positive one. Based on your experience in this ticket would you please be kind enough to rate us externally on: