razoredger

In answer to your question, we created a new testimonial widget using the testimonial widget in the available widgets area.

In other words, we dragged a testimonial widget to display area, changed title and saved,

All options were default from main testimonial widgets settings

No matter about height, Increasing character count does the trick.

It is not working 100%. You can edit but WP now is not able to register a new line in a product discription for example.

That means this is not a fix, just a ruse to prevent qtranslate from disabling.

IMHO, consequently, changing 6 to 7 in the version info is not a viable solution.

I too am waiting for a qtranslate update to work with the latest WP version.
The patch seems to work for some not for others.

I donot like the disable option, as my client is not expected to dlve into shortcodes to add or modifiy content, definitely not expected to modify code every time a core update is required.

TO MAYMARTINEZ
You website display correctly. What do you mean by “cannot see any information on my website” ? To what information are you referring?

TO PLUGIN AUTHOR.
What is your expected qtranslate plugin update date?

Nothing changed.

What I did:
1. Removed widget from web page display area
2. Reset the settings under compatilibility bxslider
3. Adjusted custom settings, max height, speed, no gravatar display, no author, etc.
4. Returned widget to original web page display area (first footer)

Regarding versions, 2.15.1 is installed.

You can see it working at this staging web, only available briefly,
https://www.stagewp.mywebpixie.com

Thank you for your help!

BTW, we have used the plugin in past projects who did not require the stop go buttons.
Currently, it is being used on a staging project, not yet live for a client who wants to stop and read each testimonial. ??

Thank you for reply.
I’m looking at compatibility settings but I don’t see what parameter is relevant to the player stop go button not displaying. Taxonomies, export, import, remove data, reset to defaults, bxslider, disabled animation…?

This functionality was annoying my client. I couldn’t see what the issue was. I knew it wasn’t ME adding hyphens as I do no proofing of “final content” before integration. In addition, I failed to find specific hyphens in editor page text.
The client remained adamant. LOL

After reading several hyphenation-related forum posts, I got here. I did the search as suggested for “word” and found nothing, but searching for “hyphen” located the offending css.

Mystery solved!

I have client complaning of the same jumpiness in IE and Firefox on a site we are building for them.

I have disabled effects for accordions and am waiting for client to confirm this resolves the jumpiness he perceives.

I would appreciate suggestions in case this does not help.

Okay, thank you for clarifying . My client does not collect fees from attendees and finds it confusing. I will need to go with an alternate event management module in that case.
Lydie

esmi, ah thanks for the precision.

Jan The issue became acute when I revised the page that sticks above the rest on the front page.

I am using the following code:

/** inserts specific page content */
$post_id = xx;
$queried_post = get_post($post_id);

echo '<h1>'; echo $queried_post->post_title; echo '</h1>';
echo $queried_post->post_content;

echo '<p><p/>';
/** above rests on top of main loop content */

I feel that instead of re IDing the latest revision of the page, WP should re-ID or rename the older versions so that the current page conserves it’s ID constant.

I did a “brute force” fix, by deleting all revisions of page except the current version in PhpMyAdmin. I then updated the page id based on the database info to the new version page id in the code.

I agree, about finding plugins solutions that use the title or slug. Especially since the latest versions of WP no longer displays page IDs natively.

Great detective work dhannigan!

I wonder what the thinking is behind the random id generator on page load.

Thanks for sharing the hack. I too hate to hack a plugin because as we all know when the plugin gets an update the hack vanishs and we will be back to square one.

Now wouldn’t it be a dream if, in this scenario, we could create a “Child plugin”, like for themes.

Thanks for the hack. I tried the autoheight function but it does nothing.

Download not available….