Forum Replies Created

Viewing 15 posts - 121 through 135 (of 623 total)
  • Author
    Posts
  • in reply to: Hide My WP – can't access to dashboard #9947
    Hassan
    Post count: 955

    Hi salabpl,

    I need more details.

    First of all, let me know how you could login to site and disable ‘Trust Network’ when you were blocked?

    Second of all, go to http://whatismyip.com/ and let me know your IP address

    Lastly, which require basic understanding of programing but very helpful:
    Open WP theme editor, choose header.php, copy entire file and save it somewhere as a backup, past below line at the TOP of the editor (before < ?php or < html) <?php echo $_SERVER['REMOTE_ADDR']; ?>

    Then, open your site and let me know IP shown at the top of the site.

    At the end remove that line from header.php and save change.

    in reply to: "HTTP ERROR 500". #9946
    Hassan
    Post count: 955
    This reply has been marked as private.
    in reply to: "HTTP ERROR 500". #9937
    Hassan
    Post count: 955

    That’s because I changed settings!

    Here is new link:
    /wp-login.php?hide_my_wp=1234

    PS:
    You no longer can access to /wp-admin without login.

    in reply to: "HTTP ERROR 500". #9926
    Hassan
    Post count: 955

    Hello,

    Seems it was fixed!

    First sorry for delay, you already qualified for a refund.

    The issue:
    It was mentioned somewhere in FAQs that HMWP may have problem with maintenance and coming soon plugins as those plugins wrap real theme with another page which confuse HMWP.

    I just removed stored settings (not easy though), disable Launcher, configure HMWP as usual and enable Launcher again. Disabling Launcher is critical for changing new admin path.

    I couldn’t re-generate first 500 error but base on what I saw in your WP directory it was an issue with incorrect or modified htaccess.

    Please check different aspects of the site and let me know if there is any further issues.

    Again, sorry for the delay.

    in reply to: Error accessing WP backend #9620
    Hassan
    Post count: 955

    Most of plugins are compatible with PHP 7.0. It can boost your site performance, too

    So I suggest to find that incompatible plugin which cause that ugly warning error then disable it or use an alternative then configure your account to use PHP 7.0.

    Hope this helps.

    in reply to: Crashed Back End #9619
    Hassan
    Post count: 955

    I approved the request yesterday. Did you get it?

    Anyway, sorry about that.

    in reply to: Problem with "WooCommerce Direct Free Download" #9617
    Hassan
    Post count: 955

    Oops, I just broke your site 😐

    Please provide FTP details or rename htaccess (in WP root directory) to something else (.htaccess_bad) to make it work again.

    in reply to: Error accessing WP backend #9480
    Hassan
    Post count: 955

    Hi-

    After doing many tests here is what I could understand:

    Without a doubt it’s a memory usage problem. It wasn’t fixed by increasing max memory limit because it was not caused because of an explicit limit but it’s an out of memory problem. In other words, if your computer has 1GB memory and you set the memory limit to 4GB it doesn’t mean you can use more than 1GB. Disabling Jetpck helped because it decreased memory usage not because there’s an issue with it.

    I configured your site to use PHP 7.0 and this completely solved the problem (Note that PHP 7 uses about 50% less memory than PHP 5.x). Unfortunately, there was an incompatibility with PHP 7 and one of your other plugins (or maybe your theme).

    As Hostgator suggested here (out of memory section), it’s better to contact with their support department.

    Send these lines as reference (74186752 means about 70MB):

    [13-May-2016 11:07:38 UTC] PHP Fatal error:  Out of memory (allocated 74186752) (tried to allocate 180224 bytes) in /home1/q3e5b0o1/public_html/wp-content/plugins/wordfence/lib/menu_scan.php on line 99
    [13-May-2016 11:07:38 UTC] PHP Fatal error:  Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0

    Let me know the result.

    in reply to: Error accessing WP backend #9456
    Hassan
    Post count: 955

    Seems strange. I also requested FTP so if it goes wrong I can deactivate the plugin.

    in reply to: Error accessing WP backend #9426
    Hassan
    Post count: 955

    Hello there,

    Sorry for delay, there was another customer with similar issue and I responded him by email. Maybe, I guested it’s a duplicate query.

    Anyway, this message may be caused by any other plugins or theme or even WP itself. In fact, WP had similar problems before. So it’s not possible for us to regenerate it.

    As, it take so long, you’re already qualified for a refund but please still follow this small guide and help us for similar issues. Even after refund you can use our plugin in your site.

    To see the real error please open your plugin editor choose Hide My WP in this file: hide-my-wp.php search for ob_starter then change this line (add // before it):

    ob_start(array(&$this, "global_html_filter"));

    to

    // ob_start(array(&$this, "global_html_filter"));

    Then check your site for any error message. If you don’t see anything please a href=”https://codex.wordpress.org/Debugging_in_WordPress#WP_DEBUG&#8221;>enable WP debug mode

    If you think it’s complex please provide credential details (WP+FTP) with a private reply and I will do it.

    Hassan
    Post count: 955

    Of course, you’re right! But topics assigned to me are usually complex and strange so I have to add them to the list and try different things to find and solve them.

    Hassan
    Post count: 955

    It was fixed by HMWP 5.1.1!

    I guess there is a small bug in current WooCommerce release. Anyway, I changed our code base to make it work!

    5.1.1 has been attached for future uses.

    Attachments:
    You must be logged in to view attached files.
    in reply to: WPThemeDetector is able to detect site #9420
    Hassan
    Post count: 955

    It was fixed using HMWP 5.1.1!

    I suppose there is a small bug in current WooCommerce release. Anyway, I changed our code base to fix it.

    Wait for few hours and try again.

    in reply to: mu broken + attack on xmlrpc #9266
    Hassan
    Post count: 955

    Sorry, I couldn’t make it work. One problem was cache I couldn’t see changes in source code instantly because of a kind of cache problem or conflict with another plugins This made debugging impossible. (I flush W3TC but not efficient)

    Do you have a database back up? Am I allowed to change plugin settings or disable themes? Site visitors may also experience problem for few hours.

    If you confirm I can go to next stage and try again.

    in reply to: 404 error on /wp-admin/customize.php page #9108
    Hassan
    Post count: 955

    I updated your site to latest stable version and disabled ‘Hide Other Files’.

    It works now!

Viewing 15 posts - 121 through 135 (of 623 total)