Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forbidden cursor #211

Open
saggel opened this issue Oct 20, 2016 · 5 comments
Open

Forbidden cursor #211

saggel opened this issue Oct 20, 2016 · 5 comments

Comments

@saggel
Copy link

saggel commented Oct 20, 2016

I'm trying to import a vbulletin database, and whilst I've filled all the needed details in the importer, I get a forbidden cursor sign when I try to hit the "start convert" button. Could someone please help me to figure why this is happening? Thank you in advance!

@saggel
Copy link
Author

saggel commented Oct 20, 2016

If this helps - and I assume it does, I get these in the logs:

> The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
  * nodebb-plugin-import
  * nodebb-plugin-import-vbulletin

I run the latest NodeBB v1.2.1, does this mean I can't use the plugin?

@bdharrington7
Copy link
Contributor

The readme is pretty clear: you need to have checked out v.1.0.0 exactly.
So no, you can't run the plugin on v1.2.1.
On Thu, Oct 20, 2016 at 2:17 AM Spyros [email protected] wrote:

If this helps - and I assume it does, I get these in the logs:

The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset -p PLUGINNAME to disable it.

  • nodebb-plugin-import
  • nodebb-plugin-import-vbulletin

I run the latest NodeBB v1.2.1, does this mean I can't use the plugin?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#211 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEV8Q8z2SVgcaKLgCEqIobAxb1WYAZXkks5q1zGUgaJpZM4Kb4C1
.

@saggel
Copy link
Author

saggel commented Oct 20, 2016

Thank you - I did, but I didn't realise it was just for a specific version thought it was for the whole v1 - thanks again!

@saggel saggel closed this as completed Oct 20, 2016
@saggel saggel reopened this Oct 20, 2016
@bdharrington7
Copy link
Contributor

Please include the stack trace

On Thu, Oct 20, 2016 at 7:56 AM Spyros [email protected] wrote:

I've created a new VPS and had a fresh v.1.0.0 installation! The problem
persists!


You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#211 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEV8Q5Ja9VKTC_mrt0FbbYH9OF4qY11Aks5q14EwgaJpZM4Kb4C1
.

@akhoury
Copy link
Owner

akhoury commented Oct 20, 2016

are u actually seeing an error or just that warning? if it's only the warning, just ignore it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants