KerryGee

Hi,

thanks for your quick reply.

> Only enable 6G rules. Do not enable 5G rules.

Ok, i did disable the 5G rule and only 6G is in .htaccess now. It would be nice to have some advice in future relases for new AIOWPS users (like me) that these .htaccess rules are mutually exclusive. I am also new to the 5G/6G rules, so this was unforeseeable to me. I was expecting the 6G is some “additonal” extra, more restrictive layer.

> In regards to the comment above, find out what part of the code added by 6G rules
> in your .htaccess file has an entry similar to the text mentioned above?

In progress. I will post the solution here.

> Let me know if the above helps you.

It did, thanks.

reagrds

K.

Hi,

thanks for your reply. By disabling all and step by step enabling “suspected” options, i found out, that three options will lead to 403 errors in phpMyAdmin:

– 6G Blacklist Firewall Rules (Enable 6G Firewall Protection + Enable legacy 5G Firewall Protection, both or single one enabled)
– Additional Firewall Rules (Enable Advanced Character String Filter enabled)

Every single option generates some 403 on some files. I guess its one or more of the very restrictive RedirectMatch inside the root .htaccess file.

Any ideas how to fix/bypass that?

regadrs

K.

I am currently testing these:

Events Manager
The Events Calendar
Modern Events Calendar

Experiences from others are welcome!

regards

K.

Can someone recommend similar free plugins?

I found a (unsatisfying) solution by my own, which seems to be the easiest and only solution applicable so far (excluding live code/parsing manipulation techniques to change the code in real-time): Change the open street map part from http to https in the OpenStreetMap.js:

OpenLayers.Layer.OSM.Mapnik = OpenLayers.Class(OpenLayers.Layer.OSM, {
    /**
     * Constructor: OpenLayers.Layer.OSM.Mapnik
     *
     * Parameters:
     * name - {String}
     * options - {Object} Hashtable of extra options to tag onto the layer
     */
    initialize: function(name, options) {
        var url = [
            "https://a.tile.openstreetmap.org/${z}/${x}/${y}.png",
            "https://b.tile.openstreetmap.org/${z}/${x}/${y}.png",
            "https://c.tile.openstreetmap.org/${z}/${x}/${y}.png"
        ];
        options = OpenLayers.Util.extend({
            numZoomLevels: 20,
            attribution: "&copy; <a href='https://www.openstreetmap.org/copyright'>OpenStreetMap</a> contributors; <a href='https://www.HanBlog.Net'>OSM Plugin</a>",
            buffer: 0,
            tileOptions: {crossOriginKeyword: null},
            transitionEffect: "resize"
        }, options);
        var newArguments = [name, url, options];
        OpenLayers.Layer.OSM.prototype.initialize.apply(this, newArguments);
    },

    CLASS_NAME: "OpenLayers.Layer.OSM.Mapnik"
});

Alternatively using a non-protocol variant would very likely automatically select https by default i guess (didnt check!):

        var url = [
            "//a.tile.openstreetmap.org/${z}/${x}/${y}.png",
            "//b.tile.openstreetmap.org/${z}/${x}/${y}.png",
            "//c.tile.openstreetmap.org/${z}/${x}/${y}.png"
        ];

Good news: Easy to implement
Bad news: Can easily be overwritten with a update/new version

Any better suggestion is highly appreciated.

best

K.

The latest version 3.3.16 seem to fix the sidebars color issue, but now the drop down menu items in the theme are semi transparent when opened ??

Update: 3.3.17 did fix that transparent issue

• This reply was modified 7 years, 8 months ago by KerryGee.

Same here!

Ok, thanks.

K.

Ok, works for me too. But why will be the CS2 deactivated and CS installed instead?

best

K.

@nicolas GUILLAUME – Very nice, thanks for fixing that issue in 3.3.11.

K.

@nicolas GUILLAUME – Could you please add the regarding element to the issue report, that has been stripped down as html inject in GitHub i guess:

`<nav id=”nav-header” …>

thanks

K.

Nice. THanks for the replies on this.

beste regards

K.

I found a way to do this after exploring the Hueman source css files and putting this in my own style.css:

@media all and (max-width: 1320px) {

/* HEADER WIDGET ZONE*/
.header-ads-desktop #header-widgets {
display: none;
}

/* HEADER WIDGET ZONE*/
.header-ads-mobile #header-widgets {
display: none;
}

.both-menus-mobile-on.header-ads-mobile {
display: none;
}
}

Maybe this can be of help to someone else.

best

K.

Hi Eli,

yes, it looks like fixed. Thank you very much. Just a note: The plugin itself consumes a lot of runtime resources and is by far the one that uses the most on my server environment. Maybe this could be a goal in future to reduce the resource-hunger of the plugin.

Thank you again for solving this.

best

k.

@aristotel_timely – Very nice! Thank you.

best

k.