Could not determine manipulator class name? [SOLVED W/ NEW VERSION]

[Jack @ PharSide]

Any idea how to fix this. I changed a lot in the styles but nothing that should cause this. Any ideas? Been searching everywhere. If I hit refresh right after, it loads fine with no error?

Error says pretty much where smarty code is used it looks like? All I get is:
Could not determine manipulator class name

Thanks as always all!

[tonyrap]

I've got the same problem with a page using the Custom Content module. When the page is set as not cacheable, as it's supposed to be, the content will not display at all, just "Could not determine manipulator class name." When it's set to cacheable, it will display correctly after refresh, but not on the first pass.

The page is at http://swanseaschoolofdance.com/index.php/news-centre

The login page that leads to it is http://swanseaschoolofdance.com/index.php/login (user: student0708, pw: peterpan)

Thanks for any help!

Tony

[Jack @ PharSide]

Sorry Mark http://www.winehistory.net/

I have narrowed it down to the FrontEndUser module as well as the CustomContent. The error happens exactly where you call those scripts. I don't have any customcontent tags in the login (FEU) page for instance and it still errors out occassionally (about 10% of the time). All other times the scripts operate as designed.

Please note I have cache pages still checked for testing.

I also have been testing it for 10 minutes and it hasn't errored out for me yet? Can't replicate it this morning? However, it did several times last night and I have not done anything. I will update this post asap.

Thanks all but if 2 of us feel it - it could be a problem. Anyone else notice it?

[Jack @ PharSide]

Ok, now the whole thing keeps blowing up. What is this?

Here is the login URL:
http://www.winehistory.net

Username: cmsms
Password: cms1234

I am getting this error all over the place. Is it a server error? It was working great then it started getting really bad with no code edits or changes. Could something on the server be getting busy with a crappy host like GoDaddy?

Thanks for your help!

[teackele]

had the same problem

i've downgraded to customcontent 1.4.6 an feusers 1.2.0 which worked, so i leave it now for the time being until the probable bug has been solved.

btw first downgraded customcontent, which didn't seem to work, which might indicate that it is somewhere a problem in the last (2 ?) versions of feusers

[rcp]

tonyrap, seems like you managed to get rid of the bug. Care to share with us how you did it?
Thanks in advance!

[Jack @ PharSide]

tonyrap, seems like you managed to get rid of the bug. Care to share with us how you did it?
Thanks in advance!

teackele had the fix that worked for me until that module is fixed:

1. Downgrade FEU to: 1.4.6
2. Downgrade CustomContent to 1.20

That worked for me. On a side note, you may also want to deactivate the "only allow one login at a time" as that causes all sorts of errors as well.

Good luck with it but these downgrades worked for me

[rcp]

Thanks!
Btw, is there any way to see if a user is logged in without using CustomContent?
Even if we have to use little {php} snippets?

[calguy1000]

CustomContent 1.4.9 should solve these problems.

[Jack @ PharSide]

Awesome CG - thanks for the upgrade

[tonyrap]

Yes thanks, the new version of CustomContent seems ok. (I seemed to have it fixed before with the FEU downgrade, but then new error messages showed up.)

It still only works with the page set to "cachable," and I don't know if that will cause other issues, as the documentation emphasizes pages have to be not cachable.

I also haven't upgraded FEU again. Has anyone tried that?

[rcp]

I also haven't upgraded FEU again. Has anyone tried that?

1.4.9 fixed the problem (thanks calguy!)

[Jack @ PharSide]

Yes, sorry. Forgot to mark as solved. Calguy's upgrade worked great!