• Resolved playbasfa

    (@playbasfa)


    Hello, when I scan the database, the plugin get stuck at 38% on the plugin “Elastic press” for a long time and then give me the error “error – Internal Server error”.

    There is a way to by-pass this plugin so that I can complete the scanning?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Vladimir Garagulya

    (@shinephp)

    Hi,
    Yes, it’s possible to manually modify skip-list.
    Add to the end of plugins/plugins-garbage-collector/data/skip-list.json file, the string:
    , "elasticpress\/elasticpress.php"
    So you should see this as the result at the end of file:

    
    "w3-total-cache\/w3-total-cache.php", "elasticpress\/elasticpress.php"]
    

    I tested PGC with this plugin installed and did not get any errors. So PGC may produce error on another plugin.
    Look if can find something related in the server log files. You can enable WordPress debug mode this way:

    Debugging in WordPress

    Thread Starter playbasfa

    (@playbasfa)

    Hello, thanks for your answer, you’re right if I skip Elasticpress I got an error on something different. If I do again with ‘something different’ i get an other error after a few % points (Elasticpress endpoint first and then Elementor Skin).

    I activated debug using
    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_LOG’, true );

    But then if I check the debug.log file I don’t see anything close to the time than I run PGC.

    Can I do something different?
    Before migrating my website to AWS the plugin was working correclty.

    Thank you,
    Fabrizio

    Plugin Author Vladimir Garagulya

    (@shinephp)

    Hi Fabrizio,

    To proceed investigation of the problem, contact me directly via vladimir [at-sign] shinephp.com

    Thread Starter playbasfa

    (@playbasfa)

    Thank you so much, I just did it ??

    Having a similar issue, is there a fix or should I email you too?

    Plugin Author Vladimir Garagulya

    (@shinephp)

    @zenixnet:

    The issue was related to the plugin with a lot (thousands) of files. Server generated the timeout error when PGC went through that plugin in a queue.

    So I helped @playbasfa to isolate that plugin and add it to the skip-list as a workaround. You may contact me directly if you need a similar help.

    I am considering buy your plugin, could you tell me the “Per plugin access for roles and users with “activate_plugins” capability” allows the permitted user to “activate” the plugin (for admin or others) only, or allows the permitted user to “use” that plugin?

    I need a lower lever user to be able to use a plugin (not just activating it), while others cannot use that plugin. I found that right now, without the paid version, there’s just activation of plugins (not “use”) to be chosen. But maybe your paid version is only for activation of certain plugins, but not for “using” it?

    And, if the permitted user is able to “use” a certain plugin, can we set that he can only “use” certain features of that plugin (not showing certain links linking to some features of the plugin that we don’t want him to use)?

    Thank you.

    Plugin Author Vladimir Garagulya

    (@shinephp)

    @vincentqin,

    Mentioned add-on allows to activate/deactivate plugins from the restricted list – user sees not full list of installed plugins.

    URE Pro allows to block unneeded admin menu items if it’s not possible to revoke related user capabilities from a role.

    P.S. It’s better to discuss URE Pro not here. Use site contact form or write directly to support [at-sign] role-editor.com

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Stuck on Elastic Press – Internal server error’ is closed to new replies.