2.8.8 template integration improvements and 2.8.8 pre-logs

[axew3]

using page-forum or shortcode?

[Ezrael]

page-forum

[axew3]

I see.
Still there is an error somewhere thrown by jQuery but looking at it i cannot reverse from where it come out at moment.

last page-forum works fine i just tested it again, there are no errors on it.
Can you try to disable the phpBB extension responsible of this dom output:

Code: Select all

/* Add resize attach in phpBB3.1 && Anvar bb3.mobi */

??

it seem to be the problem, beside that now the console return that the postmessage fail so you have to change the line

Code: Select all

var w3allAllowDomain = 'https://surferparadise.de';

not

Code: Select all

https://forum.surferparadise.de/

[axew3]

Stop here all working!
But there is a problem with css, let see as i will return in place!
It is a problem of the css and the new Resizer lib.
Let check after to fix all! You'll be there in the evening!?

I get now only
The event origin do not match

that's ok! All working except the above, let me explain after the reason and give the fix!

[Ezrael]

Yes I will be online this evening!

I change the code to

Code: Select all

var w3allAllowDomain = 'https://surferparadise.de';

I also deactivated Inline images in attachment extension but the issues are still there.

The extension isn't new and worked with 2.8.4 and the old resized without issues.

[axew3]

NONO all is working now, read above my last message!
viewtopic.php?p=6427#p6427

ps there are css problems also here where you see the iframe loading and expanding to 100%width (i see it for a moment when the page load).
It is not good, there is a problem on how the iframe is embedded. We'll fix it!

Code: Select all

The extension isn't new and worked with 2.8.4 and the old resized without issues.

exactly, with the old resizer. With the new v5 seem to have some problem instead!

ps More exactly, maybe you do not see the error because it do not cause any malfunctioning even if there is an error: it is thrown in fact on the footer, when all scripts already fired, but not the resizer (and on the new resizer lib it cause the error).
I suspect that your extension is instead exactly the problem of the js error that was coming out.
Now let fix the css, see you later!

[EDITED]