Try to be brief, the problem I have is the quick message editor.
I imported from my phpbb3 forum. Everything correctly except that the quick editor does not work. When I click "quick edit" in Firefox out a circle which means that you are working in Internet Explorer I get this error:
"" null "is null or not an object
line 11 in vbulletin_quick_edit.js "
In a message on this forum have told me the following:
Please I need help. I have the latest version of vBulletin 4.0 Gold and any plugins installed. How can I fix this? Thanks
I imported from my phpbb3 forum. Everything correctly except that the quick editor does not work. When I click "quick edit" in Firefox out a circle which means that you are working in Internet Explorer I get this error:
"" null "is null or not an object
line 11 in vbulletin_quick_edit.js "
In a message on this forum have told me the following:
"this is all a permission problem from imports. I could write pages of reports similar to this one.
the underlying problem is that VB4 importer does not "refresh" certain permission types (especially attachments, see my other reports), so you end up with users that have no right at all as far as new features are concerned. Even admins.
These permission issue generate "refusals" that have no answers in XML error message. This turns into a "javascript error" that is not really an error. It's an unexpected race condition.
(VBTEAM; I'd be glad to be added in a beta testing team, if any.)
I've manually fixed these issues, either by forcing refreshing of permissions or by editing the SQL. "
the underlying problem is that VB4 importer does not "refresh" certain permission types (especially attachments, see my other reports), so you end up with users that have no right at all as far as new features are concerned. Even admins.
These permission issue generate "refusals" that have no answers in XML error message. This turns into a "javascript error" that is not really an error. It's an unexpected race condition.
(VBTEAM; I'd be glad to be added in a beta testing team, if any.)
I've manually fixed these issues, either by forcing refreshing of permissions or by editing the SQL. "
Comment