Author Topic: Plugins State "not initialized"  (Read 7799 times)

0 Members and 2 Guests are viewing this topic.

markinfurkin

  • Full Member
  • ***
  • Posts: 8
Plugins State "not initialized"
« on: May 12, 2015, 12:45:59 PM »
i try install title notification and emoji plugins but when i click on "enable" in the plugin page, the plugins change to "not initialized" state and dont "working" for me :(
i already read all informatios, both on here(https://mibew.org/tutorials/2014/12/25/how-to-install-plugin-for-mibew-messenger-2-0) and the files "readme.md" on plugins folder, but my my doubt is in relation to this part:
these actions are must required?

1. Obtain a copy of the repository using `git clone`, download button, or another way.
2. Install [node.js](http://nodejs.org/) and [npm](https://www.npmjs.org/).
3. Install [Gulp](http://gulpjs.com/).
4. Install npm dependencies using `npm install`.
5. Run Gulp to build the sources using `gulp default`.

i used lastest version of xampp, php 5.5.24, apache 2.2
print:


TKS & REGRATS

EDIT:

I found this:
 // Actually we do not know why the plugin does not work. The only thing
        // that can be said is the plugin was not initialized correctly by some
        // reasons.
        return getlocal('not initialized');

 :-[ :-[ :'(
« Last Edit: May 12, 2015, 12:54:09 PM by markinfurkin »

faf

  • Mibew Staff Member
  • Native
  • *****
  • Posts: 951
    • Mibew Messenger
Re: Plugins State "not initialized"
« Reply #1 on: May 12, 2015, 03:01:01 PM »
You quote the section named 'Build from sources'. It has nothing to do with the installation process which is described in the 'Installation' section.

markinfurkin

  • Full Member
  • ***
  • Posts: 8
Re: Plugins State "not initialized"
« Reply #2 on: May 12, 2015, 04:28:38 PM »
do you have any suggestions in this case when appear "not initialized"?
« Last Edit: May 12, 2015, 06:07:50 PM by markinfurkin »

Dmitriy Simushev

  • Moderator
  • Native
  • *****
  • Posts: 345
Re: Plugins State "not initialized"
« Reply #3 on: May 13, 2015, 06:19:54 PM »
This message is shown when the plugin reports to Mibew that something is wrong. Check apache's error log for details about the problem.