HELP... moved 7.0.9 site, can't post in Orca Forum

I need some help.  I recently moved a D7.0.9 site from a VPS to a DS and now members cannot post in the Orca forum.  They get a error stating they have not entered enough characters when they have (verified).  When I try to reply to a post, the edit screen does not load (but see "loading" at the top).  Plus the buttons in TinyMCE do not work, e.g. dropdown option don't show... but only for the Orca Forum (TinyMCE works elsewhere on the site).  

I had this same/similar issue a little over a year ago and was able to solve it but now I've forgotten how I did it.  

I tried recompiling the Forum language file and that appears to have no effect.  Anyone remember how to fix this.  Is there something unique to the hosting company that must be updated?  (For those curious, I moved from TMD to OVH.)

TIA, 

Paul

 PM site

This sounds like the canvas_init.xsl is the problem, both in /base and /base_en; /modules/boonex/forum/layout/base/xsl/canvas_init.xsl.  Check to see if they are missing or corrupted.

By the way, in 7.0.9 (and in 7.1 as well) tinyMCE init is separate from the site and the forum, it is the canvas_init that handles it for the forum.

Do you know if the server was compiled with xslt or not ?  the forums load so i am not sure 100% if that's the issue. 

I would also try and clear your web browser cache completely as well or try a browser that you have never been to the site with yet. 

UNI default template or 3rd party template ?

The new server run with 755 644 perms or 777 666 perms ?

The new server running with the same user and group as the old server ?

Did the old vps server run memcache or apc ?

@ dolphin_jay ... looks like a good list of items to check for issues... thank you.

Don't push my advice aside too quickly; when I was trying to upgrade TinyMCE back in 7.0.9, what you described was happening with me; exactly.  It could be related to the javascripts that canvas_init loads as well.  At the time I just dropped upgrading TinyMCE and waited for Boonex to do it.

@ geek_girl ... I'm not brushing your comments aside.  I went through the exact same thing 482 days ago as you did a while back.  In my case I upgraded to the lastest TinyMCE while setting up a new site under D7.0.8 (see my forum post http://www.boonex.com/forums/topic/Tinymce-in-Orca-Forum-stopped-working.htm).   I tried for several hours but could not solve it and I could not undo the upgrade... it was a bit frustrating.  My solution was to start over again when D7.0.9 come out several days later *and* not upgrade TinyMCE.

It was working just fine on the TMD VPS.  I have no idea what's changed... but I'm looking.  Using Firefox debug tools, it appears to be a JavaScript error... something is undefined but I the error does not say exactly what it is.  Chrome/Iron reports: Uncaught TypeError: Cannot call method 'replace' of undefined

Anyone have some idea of where I should look next?

How did you transfer your site from the VPS to the dedi?  I am wondering if it is a path related error.

You could export the forum tables so you have the forum topics and boards; not sure of all the tables involved so check.  Then uninstall the forum module and reinstall.  Then you could import the tables back.  I know you really don't want to have to go to all that trouble.

We had a forum issue; can not recall what now, and one of the team suggested that.  Another member of the team had spent hours setting up boards and entering starter topics and the last thing I wanted to do was to uninstall the forum.  I manage to get whatever it was resolved without having to go through the whole uninstall/reinstall/import data routine.

I'm not sure if uninstalling and reinstalling the forum is the solution. 

I just tried adding a new Forum Topic in several browsers... out of 9 attempts, two worked.  It did not work in the latest versions of Iron, Chrome, Firefox, Opera and Safari (32bit Win7).  It also did not work under IE 9 or 10... *except* when switched to compatibility mode... then both worked as they should... which puzzles me.  Any idea why?

When I traced the error in FireBug, the error was "An invalid or illegal string was specified" while loading the jquery.js file. 

That's as far as I've gotten.

I am afraid that my brain is going to be too small to help with this one.

Prashank fixed it... the guy is nothing less than amazing when it comes to debugging puzzling code problems.  The problem had to do with TinyMCE and how the Forum loaded it... something to do with the GZ loader (with old browsers don't use). 

Can you share the fix?

@ geek_girl ... It was a process of narrowing down where the problem was.  We worked on it together with Prashank making changes and me helping with testing.  We setup a fresh install of D7.0.9 on the *same server* setup to verify posting to the Forum worked correctly and to have working copy of "clean" code to compare to.  We first swapped in the "clean" copy of the /modules/boonex/forum/ folder and found no difference.  Next, we swapped in the "clean" copy of the /plugins/tiny_mce/ folder and found the problem gone.  But since I wanted the TinyMCE upgrades we need to figure out what exactly the problem was. Prashank deduced it was one or more of the several editor plugins that I'd added to TinyMCE... then narrowed it down to: fullscreen, embed and imagemanager.  When we only removed them the Forum's TinyMCE would load correctly.  But I still wanted them so Prashank re-added the three buttons, placing them as the last three buttons on the bottom (third) row... and TinyMCE worked.  Neither of us know why removing then re-adding those three buttons, and having them load last, solved the problem... but I'm happy it's working now.

One of the mysterious that only the gods knows LOL.  Oh well, at least it is working; that is the main thing.

The problem started again (no idea why).  This time we kept digging until we found the exact problem.  In the canvas init code, used for the TinyMCE buttons, there was an extra "|" that shouldn't have been there...  

in our case the code: param[name|value|]
... should have been: param[name|value] 

-- Paul