www programming

I also think it is time to add option for the page-forum, to let choose at what gap/distance, the iframe should scroll to.
Since themes headers are of different heights, an option about this will be useful to complete with easy the template integration.
Stay tuned lovely and cool people!

https://www.axew3.com/w3/forum/?cool=cG9zdGluZy5wa

https://www.axew3.com/w3/coding/?cool=cG9zdGluZy5wa

thinking that to be inline with myself (not because i'm cool, but just because i often use the word in many contests) i will name the w3 var in 2.2.1 on this online install, into [i]cool[/i]:
[code]https://www.axew3.com/w3/forum/?cool=cG9zdGluZy5wa[/code]
maybe i will switch into
[code]https://www.axew3.com/w3/coding/?cool=cG9zdGluZy5wa[/code]
with peace of mind about SEO ...

nope, just joking (but not about SEO consideration)

P.s suggest hints and report bugs!

May it was obvious to imagine, that the stupid line of code added via jQuery, to switch href links into widgets onmouseover (seo trick), may fails when jquery not added by default by used theme.
So this is not strictly v5 code related, by the way js related this plugin.
It will be fixed on soon coming 2.1.1, replaced by pure js instruction.
At this time, the v5 js code will be also released, updating page-forum to fit new feature Fancy query Url.

Ehy cool people! Too late!? Never say never ...
[i]The infamous w3 ...[/i]
The Fancy url is coming soon with v5 iframe code!

[attachment=0]w3all Options -fancyURL.png[/attachment]

p.s it's necessary to exchange some name into buttons and Options names ... they are little different now on behaviors, like:
the login widget do not point anymore to phpBB, so the fact that the setting about [i]links to point to phpBB real url or iframe wp page[/i], not affect anymore. Further more, to point WP login-logout-register links to phpBB, there is already added in the past a specific option.

The v4 code js code has been just updated, since it was giving error on copy/paste or containing an unwanted char.
I've not verify why i copied it and was failing when applied into overall_footer.html.
[quote]I just can say, like many others, that the new WP Gutenberg is a total mess sometime.[/quote]

if(w3iOS == false){
var bd = document.getElementsByTagName("body");
for (var i = 0; i < bd.length; i++) {
var bdID = bd[i].getAttribute("id");
}
var elt = document.getElementById(bdID);
elt.setAttribute("style", "position:fixed;top:0%;left:0%;width:100%;margin:0px;");
}

if(w3iOS == false){
$(window).on( "load", function() {
var bd = document.getElementsByTagName("body");
for (var i = 0; i < bd.length; i++) {
var bdID = bd[i].getAttribute("id");
}
var elt = document.getElementById(bdID);
elt.setAttribute("style", "position:fixed;top:0%;left:0%;width:100%;margin:0px;");
});
}

Nope ...
it seem that to fix the issue about correct iframe height, it is necessary to re-add old code like this, into js [i]overall_footer.html[/i] added code:

it was lately switched to:
[code]if(w3iOS == false){
var bd = document.getElementsByTagName("body");
for (var i = 0; i < bd.length; i++) {
var bdID = bd[i].getAttribute("id");
}
var elt = document.getElementById(bdID);
elt.setAttribute("style", "position:fixed;top:0%;left:0%;width:100%;margin:0px;");
}[/code]
BUT it need to return to be:
[code]if(w3iOS == false){
$(window).on( "load", function() {
var bd = document.getElementsByTagName("body");
for (var i = 0; i < bd.length; i++) {
var bdID = bd[i].getAttribute("id");
}
var elt = document.getElementById(bdID);
elt.setAttribute("style", "position:fixed;top:0%;left:0%;width:100%;margin:0px;");
});
}[/code]
so the iframe code has been updated to fix this reverting this piece of code to what +- was.

All will be cleaned up of redundant code and more fixed on soon coming iframe v5.
In the while all seem to return to work fine just in this way.