FOP2 White Label-- Plugin Registration
-
-
If your customer bought a plugin they received an activation code via email, and you must apply that code via the server command line:
/usr/local/fop2/fop2_server --upgrade --code XXXXXXXXX
where XXXXXXXXXX is the upgrade code received for that plugin.
Best regards,
-
-
What did your customer did exactly? If they purchased a plugin, then the only way to activate it is via the command line. In general, to license any software you need superuser privileges.. it is not something unusual. There are many plugins that can be installed via web, that are free and require no license, that is why I ask what did your customer do. In any case, plugins are installed once, at setup time, and then they will just work.
-
They purchased the plugin from the Admin page. When you have the non-white label version you can enter the license code from the web page can you not? Why not be able to do that for the plugins as well. Or am I just being in informed on how your licensing works? If I were so inclined I could create a page to do this could I not?
-
Plugins are more complex to handle that standard activation. You must restart FOP2 (not reload), when a plugin is installed. And restarting is something you cannot perform via web (privilege issue). So even if the option to enter an activation code is done via web, you will still need to restart the FOP2 service, something that cannot be done via web. Anyways, I will see if I will add the option to enter plugin upgrade codes in the FOP2 Manager page on a future release.
-
HI,
I ssh'd into the system and tried to run the command:
/usr/local/fop2/fop2_server --upgrade --code XXXXXXXXX (inserted the code where the XXXX are)I waited 5 minutes with no activity so I did a Ctrl C to stop the process. Does FOP2 need to be stopped for this to work? If not what can I do to get this working. The system is a Freepbx Distro version 12 He already has the Whitelabel edition FOP2
-
Hi Ed,
It should be nearly instant, and FOP2 does not need to be stopped. You can try removing the /tmp/par-root directory and try again:
rm -rf /tmp/par-root
/usr/local/fop2/fop2_server --upgrade --code xxxxxxPlease contact me via the live help if you can, I am online now, so we can troubleshot interactively instead of via forum posts.
-
-
-
-
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login