Forum Replies Created

Viewing 8 replies - 46 through 53 (of 53 total)
  • Thread Starter deadparrotsoftware

    (@deadparrotsoftware)

    We own the server. We have both root and admin access, and all our other plugins write to that directory without any issues at all. It is NOT a permissions thing – and yes, we double checked that. And the logs I posted before ARE what it shows after we try saving.

    And while I understand this is not a “make a living” thing, people are more inclined to donate when things actually work. We have 14,300+ WP users on our list, but we can’t evaluate for them how well the plugin works because we can’t get the file to load the program it needs.

    Based on the debug we already ran, the plugin is faulting before it even tries to write the file – i.e., it never reaches the point of trying to write the file. The error is occuring BEFORE that point. I am guessing that some condition that needs to be met before the cache php is actually written is either not being met or not even being tested.

    Sid

    Thread Starter deadparrotsoftware

    (@deadparrotsoftware)

    We are still getting the message

    “Advanced cache file is yet to be generated, please save » WP-FFPC Settings”

    despite reviewing every settting multiple times and saving settings dozns of times.

    We have not given a review or rating yet, but the plugin and support so far has been dissappointing.

    Sid

    Thread Starter deadparrotsoftware

    (@deadparrotsoftware)

    The point of hiding it, is because of the brute force attacks occupying the site.

    And that was my point. It is a membership site, with login and registration buttons everywhere. Every site has at least one button – linked to a url – people click to login, so it is hardly a secret. It would fool a bot that does NOT walk the site looking for the login link.

    Sid

    Thread Starter deadparrotsoftware

    (@deadparrotsoftware)

    lol – woops! Had three windows open, typed in wrong one. apologies. 🙂

    Sid

    XML-RPC on WordPress is actually an API. If you disable the XML-RPC service on WordPress, you lose the ability for any application to use this API to talk to WordPress. It is used heavily by phone Apps that interface with WordPress sites. You need a solution that both blocks the brute force attacks and does NOT require disabling XML-RPC.

    Sid

    Thread Starter deadparrotsoftware

    (@deadparrotsoftware)

    It shoes:

    [16-Oct-2015 16:47:55] PHP Warning: include(): Failed opening ‘/var/www/vhosts/AppBuzzinga.com/httpdocs/wp-content/advanced-cache.php’ for inclusion (include_path=’.:’) in /var/www/vhosts/AppBuzzinga.com/httpdocs/wp-settings.php on line 65
    [16-Oct-2015 16:48:27] PHP Warning: include(/var/www/vhosts/AppBuzzinga.com/httpdocs/wp-content/advanced-cache.php): failed to open stream: No such file or directory in /var/www/vhosts/AppBuzzinga.com/httpdocs/wp-settings.php on line 65
    [16-Oct-2015 16:48:27] PHP Warning: include(): Failed opening ‘/var/www/vhosts/AppBuzzinga.com/httpdocs/wp-content/advanced-cache.php’ for inclusion (include_path=’.:’) in /var/www/vhosts/AppBuzzinga.com/httpdocs/wp-settings.php on line 65
    [16-Oct-2015 16:48:53] PHP Warning: include(/var/www/vhosts/AppBuzzinga.com/httpdocs/wp-content/advanced-cache.php): failed to open stream: No such file or directory in /var/www/vhosts/AppBuzzinga.com/httpdocs/wp-settings.php on line 65
    [16-Oct-2015 16:48:53] PHP Warning: include(): Failed opening ‘/var/www/vhosts/AppBuzzinga.com/httpdocs/wp-content/advanced-cache.php’ for inclusion (include_path=’.:’) in /var/www/vhosts/AppBuzzinga.com/httpdocs/wp-settings.php on line 65
    [16-Oct-2015 16:48:54] PHP Warning: include(/var/www/vhosts/AppBuzzinga.com/httpdocs/wp-content/advanced-cache.php): failed to open stream: No such file or directory in /var/www/vhosts/AppBuzzinga.com/httpdocs/wp-settings.php on line 65
    [16-Oct-2015 16:48:54] PHP Warning: include(): Failed opening ‘/var/www/vhosts/AppBuzzinga.com/httpdocs/wp-content/advanced-cache.php’ for inclusion (include_path=’.:’) in /var/www/vhosts/AppBuzzinga.com/httpdocs/wp-settings.php on line 65
    [16-Oct-2015 16:49:53] PHP Warning: include(/var/www/vhosts/AppBuzzinga.com/httpdocs/wp-content/advanced-cache.php): failed to open stream: No such file or directory in /var/www/vhosts/AppBuzzinga.com/httpdocs/wp-settings.php on line 65
    [16-Oct-2015 16:49:53] PHP Warning: include(): Failed opening ‘/var/www/vhosts/AppBuzzinga.com/httpdocs/wp-content/advanced-cache.php’ for inclusion (include_path=’.:’) in /var/www/vhosts/AppBuzzinga.com/httpdocs/wp-settings.php on line 65

    sid

    Thread Starter deadparrotsoftware

    (@deadparrotsoftware)

    You REALLY need to add the option for the admin to record/log ALL the attempts.

    Authorities and techs trying to analyze an attack require more than a few entries in the Logins and logouts tab.(live traffic is off because we enable falcon)

    – Sid

    Thread Starter deadparrotsoftware

    (@deadparrotsoftware)

    yes PLEASE do. Not everybody likes to read online, or try to memorize what a video “teaches” and you can’t make notes on the page where they apply.

    I read manuals during lunch and other times, we use them in meetings, etc. The quick start guide has a LOT of useful information, but is a pain to read with those open/close arrows.

    AND while you are at it – I guess it never occurred to anyone we might want to print various KB articles?

    I printed a half dozen or so to give to my crew – marked up to say “I want this done this way” and used up an entire ink cartridge because the code examples are have white font on solid black background! It cost more to print 2 dozen KB articles (in ink) than it did to become a PRO member! You might want to change that as well. 🙂

    Sid B.
    [Signature moderated]

Viewing 8 replies - 46 through 53 (of 53 total)