Hassan

[Hassan]

Hello-

First sorry for such long delay,

In fact, this is a complex problem and technically WP API do not allow us to handle it.

Anyway, we will release a newer version of HMWP tonight, which has new ideas to overcome this issue. Unfortunately, these ideas are not perfect solution but may be helpful.

Just disable hiding other WP files from general tab or add login query (?hide_my_wp=1234) to customize page (in our upcoming version)

A testing version is attached. You are also qualified for a full refund.

Attachments:

You must be logged in to view attached files.

[Hassan]

Thanks, this was fixed.

Please wait for final 5.1 version today or tomorrow!

[Hassan]

Seems there’s an important bug here:

Could you please share login details privately to take a deeper look?

[Hassan]

Yes, it was fixed by new IP to country provider!.

Test it and let us know result.

[Hassan]

Hi-

I think I found the problem! It was caused because you changed site and home URL by wp-config.

I commented these two lines: (add // before them)

define('WP_HOME','http://www.soe-ing.de/');
define('WP_SITEURL','http://www.soe-ing.de/');

Instead, I used WP general settings page to add www to site and home URLs, logged out and logged in and it was fixed!

[Hassan]

Please also stick in your mind installing the plugin is not duty of our staffs. They usually do it kindly to make you happy but that doesn’t mean they have to do.

More details: http://codecanyon.net/page/item_support_policy

[Hassan]

Try again and let me know the result.

I changed main.css to style.css

[Hassan]

It looks correct to me.

It may be caused by your browser cache. I re-generated the cache. Clean browser cache and try again!

[Hassan]

Was fixed 🙂

I just replaced two lines in the top of your style.css (child theme)

Something like below

@import url("../look/style.css");
@import url("../custom_css_for_filter.css");

changed to

@import url("https://www.londontradition.com/skin_main/style.css");
@import url("https://www.londontradition.com/skin/custom_css_for_filter.css");

Remember, if you change new theme path or new stylesheet name in HMWP you need to update those lines.

• This reply was modified 8 years, 10 months ago by Hassan. Reason: fix the issue

[Hassan]

Hi-

Just disable hide admin feature and full hide (general tab) and try again. Maybe even one of them can solve the problem.

Another idea is to add your secret and query to those URLs. Something like this:
domain.com/wp-admin/authorize/fb.php?token=123&hide_my_wp=1234
(hide_my_wp=1234 is the default key)

PS:
Do you mean that specific plugin copy a new file to your wp-admin folder? Then What’s the file name?

[Hassan]

Well, full hide mode is totally different with full replace mode! It’s a check option.

As I said it may still create that cookie but it’s not functional. If it’s important to not create that cookie you need to edit our source code.

Open load.php in HMWP directory and change following lines in the top of that:

if (!isset($_GET['style_wrapper']))
    setcookie($this->access_cookie(), 1, time() + 60 * 60 * 3);//3 hours

With this:

if (!isset($_GET['style_wrapper']) && $this->opt('full_hide'))
    setcookie($this->access_cookie(), 1, time() + 60 * 60 * 3);//3 hours

This was added to our upcoming update, too.

[Hassan]

Hello,

Simply disable full hide mode (general tab) to avoid that kind of cookie.

It may still create that cookie but it’s not functional and can’t invalidate caches.

[Hassan]

This reply has been marked as private.

[Hassan]

Hi-

First, sorry for such a long delay,

Seems HMWP is not activated on your side. Could you please check provided credential details? I couldn’t login to test settings.

WP itself is still hidden on builtwith at least our demo site (http://builtwith.com/hide-my-wp.wpwave.com) but there is still some revealed plugins.

[Hassan]

Hello there,

First sorry for such a long delay.

It seems it’s a bug with AAM (Advanced Access Manager). I disabled it and everything worked well.

As ‘skye’ is an administrator with all access permissions I think it’s better to contact with that author and report the problem or use an alternative plugin.

[Author]

Posts