razoredger

To produce relative links, I simply left the base url blank. The result are links beginning with /wp-content for files and /pagename/ for pages.
I uploaded it to a different url and everything displays correctly.

However any CDATA `
/* <![CDATA[ */
var abtSponsorFlipwall = {“stylesheet”:”http:\/\/www.yourdomain.com\/wp-content\/plugins\/sponsor-flipwall-shortcode\/styles.css”,”speed”:”350″,”direction”:”lr”};
/* ]]> */`

remains unchanged and I did need to do a search replace, but they were few, specific plugin related.

Any dynamic stuff is lost still, such as dynamically generated document icons.

Looked like a promising plugin, disappointing. Attachments donot show up.

To search the CSS, you need to open open the file in your HTML editor or notepad and use the search or find tool.

Glad to hear you got it sorted.

Sounds like the qtranslate update did not “take” and disabled itself.

Do the pages still display correctly per language?

I had an issue after update where all non-english content in pages and posts was wiped, and replaced with “post_content”

Fortunately I have a mirror site and was able to recreate the french language content again. A pain though…

I am using several widgets that switch languages between French and English, such as Testimonials, Tag Cloud.

Widgets to be translatable must be localized, if they are, they can be translated and switch the same as did the original plugin in my experience.
If no localization code exists in the plugin template, then no translation will show until that code is added. See plugin localization for that.

In the case of widget titles translation, I have used the title short codes successfully when title translation was not available such as for menus.

@tayssir.ch

The patch does not always work…
Why don’t you try the alternate plugin? It does the same job, is up to date: mqTranslate

@greg007 Sure, if you mean undoing the version number patch on qTranslate before updating it, why not. I’m not sure it would be necessary to do so however since any update overwrites version stuff in the plugin.

Personally, as soon as I switched to the mqtranslate plugin and found it did the job, I deleted qtranslate altogether as it interfered and was not required. No data, style or functionality loss was observed. It just works.
BTW, here’s the link to the alternate plugin: mqTranslate plugin

IMO, switching plugins to mqtranslate is the preferred solution due to the fact that doing so adheres to WordPress website security advisories to implement currently maintained up-to-date plugins within the latest WP version environment.

“Patches” are proposed to qtranslate, are help, much like duct tape fixits, made for the short term.

Check out mqtranslate plugin to get compatibility with WP 3.7.1. It’s a fork of the other,is totally 3.7.1 ready and picks up all your qtranslate stuff.

Glad it did the trick!

Halt on mouseover suits our clients needs perfectly.

Thank you for your offer of deeper support.

What is your post about? just curious… or are you just occuping space in the comments?
Lack of qtranslate compatibility with current and future WP versions is a big issue for clients who need to be able to update through the WordPress dashboard. They are not comfortable hacking php templates or just ignoring recurrent WordPress Core new version availible update messages that dominate the dashboard.

In that light, it would be good if the plugin author could advise whether plugin will be maintained current and give an approximate update date for current version.

In the event he can no longer assume such tasks due to other commitments, alternate language plugins should be preferred for live sites.

Thank you for all your help, especially checking out the widget on my project.
If your conclusions are correct, that it is a theme conflict, then I will look into that angle.
I will probably go with adding a tip to indicate mousever halts the slider.

It loos like you need to reset your permalinks.
To do that, go to permalinks, reset to links to default, save, check all pages display, return to permalinks, set to your custom choice, Mine are set to post-name so the url contains keywords), save. You should now see your pages again.