Gabe Shackle

Are you viewing a cached version of the stylesheet? When I go to:

https://taspas1po.fr/

The text is properly aligned to the left in the autocomplete area.

Hi Alex,

Try adding this line anywhere in your style.css file:

`.ui-menu-item { text-align: left; }

Let me know if that fixes it for you. I suspect the alignment is being picked up from the text-align: center; that is in the body style declaration.

Hi Alex,

This is probably due to a conflicting CSS declaration that is centering your text within LI elements. If you could post a link to the CSS for your site I can take a quick look and find out which one is causing the problems. Thanks!

Gabe

Hi AmyZealand,

Could you try updating to the latest version (1.0.8+) and see if this issue is resolved? It appears that the values for the minimum character count for the search trigger was set to nothing in the admin and the generated scripts were choking on that.

you can reach me at: gabe -at- hereswhatidid -dot- com

Could you email me a screenshot of the error you’re getting? I’m unable to recreate that here on my end. Thanks!

One thing to check is whether or not you have Accessibility Mode enabled. Try going to the Widgets page and expand the “Screen Options” area. If it’s enabled, disable it. Having that enabled will turn off the drag and drop functionality of the widget admin.

I went ahead and removed those deprecated function calls. Try upgrading to 1.0.6 and see if that also clears up the notices you were getting. I don’t get any warnings on my install with debug turned on after upgrade to 1.0.6. Thanks!

Could you email me the settings you have in place on your blog? I’m unable to recreate this issue here on a fresh 3.1 install running TwentyTen. Thanks!

It definitely is not related to just a plugin. I had the same experience AardvarkGirl had with a completely fresh install still generating the infinite loop on a Windows server.

Not sure if this is the best way to do it but you could try adding this line to your theme’s functions.php file and see if it temporarily fixes the issue:

remove_filter(‘template_redirect’, ‘redirect_canonical’);

Basically disabling the canonical redirects which I believe are the real culprit behind the redirect loop people are experiencing.

So does this qualify as resolved or is there a “kinda resolved but not ideal” option?

I just tried that plugin linked by jarnez on my dev environment and that appears to get it working again. Perhaps this will clue the dev team in as to what might be causing this issue.

https://www.ads-software.com/extend/plugins/permalink-fix-disable-canonical-redirects-pack/

I’ve gone through all those steps and it’s still going into the infinite loop on permalinks that do not include /index.php/ at the beginning or are just using the /?p= format.

Are you running this on a Windows server? This seems to be the common thread amongst the other posts I’ve found with the infinite loop issue.