• Resolved ialima7

    (@ialima7)


    When I try to access the backend:

    Warning: require_once() [function.require-once]: Unable to access app/settings_page.php in /home/user/public_html/_/noticias/wp-content/plugins/wpematico/wpematico.php on line 34

    Warning: require_once(app/settings_page.php) [function.require-once]: failed to open stream: No such file or directory in /home/user/public_html/_/noticias/wp-content/plugins/wpematico/wpematico.php on line 34

    Fatal error: require_once() [function.require]: Failed opening required ‘app/settings_page.php’ (include_path=’.:/usr/lib/php’) in /home/user/public_html/_/noticias/wp-content/plugins/wpematico/wpematico.php on line 34

    https://www.ads-software.com/plugins/wpematico/

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter ialima7

    (@ialima7)

    I solve this by renaming the plugin folder to force the deactivation. After I upgraded to the latest version.

    Versions were:
    Wordpress 4.3.1
    WPeMatico 1.2.4

    I have no idea what may have caused the problem. I have another installation with plugin activated and was functioning normally.

    Plugin Author etruel

    (@etruel)

    Hi

    Unable to access app/settings_page.php
    failed to open stream: No such file or directory

    Sounds like you have a bad installation and lost the file ‘app/settings_page.php’

    Do you tried to install again after that ?

    Thread Starter ialima7

    (@ialima7)

    The problem returned.

    So I followed his suggestion. I reinstalled the plugin.

    Must have been a an upgrade corruption, I was in the “app” folder and the file “settings_page.php” did not exist.

    Therefore, I believe the problem does not happen more.

    Thanks @etruel.

    Thread Starter ialima7

    (@ialima7)

    @etruel, help me!

    The problem returned.

    Something is deleting the file “settings_page.php”!

    I reinstalled the plugin yesterday and today the file “settings_page.php” had disappeared.

    Including the zip file of the plugin that I left in the plugins folder has been deleted.

    Does not make sense.

    Plugin Author etruel

    (@etruel)

    Thread Starter ialima7

    (@ialima7)

    @etruel

    The hosting support reported that the plugin has a security hole that opens server ports for attacks. So the anti-malware system is sending the file to quarantine.

    The host’s response was:

    nosso sistema anti-malware, trojan e virus está identificando que seu plugin é malicioso, e por isso, enviando ele para quarentena.
    Esse plugin possui código malicioso que, quando instalado, abre portas de invas?o para o servidor a hackers.

    Aconselho procurar por outro plugin que fa?a o mesmo.

    Qualquer outra dúvida estaremos sempre à disposi??o.
    Atenciosamente,

    Bruno
    Suporte SempiHost
    https://www.sempihost.com.br

    Thread Starter ialima7

    (@ialima7)

    I had not seen her answer. I foward the topic to the hosting support, we will see if they will unlock your plug-in in Apache.

    There’s no way you try to make contact with the Apache developers to inform the false-positive?

    Plugin Author etruel

    (@etruel)

    Apache is just the web server. Is not related with antivirus.

    You gets from your host an “human automatic response”. Is the common response without check the file.
    The file is open, is very short (around 600 lines), anybody can see inside the code and has not any malware.

    Is just the php functions base64_encode and base64_decode used for store the passwords in database.

    In the future I’ll try to remove these functions but is not possible for now.
    If you don’t use SMTP you can delete the lines for yourself.

    Thread Starter ialima7

    (@ialima7)

    Very thanks for you answer and support!

    But…

    I do not use the SMTP resources, could you please tell which lines to delete, exactly?

    I appreciate your help.

    And it will be even registered here to help others.

    Plugin Author etruel

    (@etruel)

    ialima7 yesterday was released a new version 1.2.5 without use of php functions base64_encode and base64_decode in settings_page.php

    Could you tried if is working now ?

    Thread Starter ialima7

    (@ialima7)

    Man, you are awesome!

    Thanks for you wonderful support and professional solution!

    Instead, I tried to intermediate a solution with the hosting but they were uncompromising.

    Many thanks @etruel! For the plugin and for the support.

    P.S.: great changelog note ??

    Plugin Author etruel

    (@etruel)

    happy to help ??

    Thanks for your words and if you can take a minute, please Rate 5 Stars on WordPress.

    Thanks!

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Fatal error’ is closed to new replies.