Extended Training & PHPbb 3.2 (including PHP 7.1)

[Keiji]

Hello everyone, and-
WELCOME TO 2018!
Well, I already said that once. But now I really mean it!

Last night was a bit of a busy day for me, and I'm sure for others as well. The site finally updated to the latest version of PHPbb, a thing we've been holding back on doing for quite a while due to reported issues on the versions including other matters on a more personal nature.

But here we are! Welcome to the new current beautiful version of everything. The great thing about this is how things will be so much smoother and faster now as rendering and processing of data is much faster.

Now, unfortunately there is, as there usually is with these things a few bugs and kinks.

I'll list those below and update as we move along, and I try to fix them all. But first I want announce it to all.

if you haven't trained yet, don't worry! training will be extended until Monday night. this means that if you were delayed or wasn't able to train due to the update. You have an extra day to do that.

I want to say first off that I did a doozy, I should have been wiser and instead done all this on a Friday, or Saturday to give time to fix things, or even done this update in a testing environment beforehand. (Unfortunately there's some variables that just isn't easy to replicate, like extensions that just won't be removed.. Like small unchanging cancerous cells in a key organ, so we gotta live with it..)

But all that is besides the point. I'm sorry.

Now let me list the issues we have so far. (If you want to see progress on these, check the announcement channel on Discord)

The points extension that we use for our yen doesn't want to be enabled for the a reason I'm still trying to determine. It's for the moment my top priority to fix. I hope to have it fixed within this coming week.
Please note: your yen totals are backupped and safe. So if we lose it somehow I still have it all logged and can easily add it again.

There's a lot of BBcode that looks and even works differently than they used to. So far I have determined it's due to a different bbcode parser engine, (basically changing the behaviour of the markup html replacer) and I'll try to find a way to make it all work again. But for the moment I'm afraid you'll have experiment with it all. Most of them do in fact work, but they behave differently than they used to.

There's also reports of an error that sometimes come seemingly at random with a white screen and an error message. I'm also looking into this and will report it to PHPbb.

If have an issue or see the error message mentioned above. Send it my way. I want to see how many there are, and how prevelant it is for everyone.

That's all for now. I'll try and keep you all updated.

 

[Keiji]

While we're still working on fixing the yen module, thanks to the help of Izumi from Leaf we've got one fix for our BBcode needs.

So far we've discovered that, the BBcode parser engine is vastly different in 3.2
What it means is that, while normally the bbcode would just parser html as is, (enabling us to use stuff like the bloodline, and rules bbcode tags, which was nice!)
But now what it does is, it parses the whole post as xml files and then renders the bbcode through that. And while it does make the size of the posts smaller. It renders a lot of our custom bbcode to act vastly different. (this is a huge discovery and could help us in figuring out how to fix our code.)

But in this discovery we found a quick fix for our spoiler tags. This is an extension instead of just a regular bbcode, (even though it works like a bbcode)
This means that all spoiler tags are automatically converted, but spoilernames should be changed to spoiler="" (insert name between the quotation marks.)
I'm aware it might not be the prettiest solution. We'll style it all up so it's pretty again soon.

Spoiler

test

Spoiler: test

test

[spoiler]test[/spoiler]
[spoiler="test"]test[/spoiler]

 

[Keiji]

We got a new table!
And while I'm scared to say that this might become our oh so favored tag of col's replacement. I will still try and see if there is a way to simplify it.
But for now. I want to throw this one out there due to it's potential in fixing all our problems with col. And bbcode in general.
And unfortunately it's a bit of a complicated bbcode for those who aren't familiar with tables/rows/columns in html. So I'll try and give a quick crash course in it.

The code is super fast to implement. When you're in your full editor panel you should see a new button next to "font colour" (note I have the dark theme, so it might look slightly different for you)

Click it, and you should see the image I spoilered below.

Spoiler

Here's a hint: When you have this menu opened, you can click the "show table guidelines" to get an indepth guide on it's functions.

The code looks like this:

[size=4]Table Title[/size]
[table=30,null]
	[thead]
		[tr=textleft]
			[th=50,null]Title1[/th]
			[th=50,null]Title2[/th]
		[/tr]
	[/thead]
	[tbody]
		[tr=bg2]
			[td=null,1]Text11[/td]
			[td=null,1]Text21[/td]
		[/tr]
		[tr=bg1]
			[td=null,1]Text12[/td]
			[td=null,1]Text22[/td]
		[/tr]
	[/tbody]
[/table]

The above is a table with a header, 2 columns, and 2 rows. This is your basic setup.
You can remove the thead tag and it's contents, if you don't want a header.
each tr is a new row, meaning if you add another tr you add a new item below it.
Meanwhile td is the column.

Most importantly. That top number in the table= part of the code is the width of the table in percentages. So if you make it 100 it'll take up the full screen.
So if you want to replicate the glorious col bbcode you can just copy-paste the following:
Replacing Text1 and Text2 with your column content. (and yes, bbcode does render inside of it!)

[size=4]Table Title[/size]
[table=100,null]
	[tbody]
		[tr=bg2]
			[td=null,1]Text1[/td]
			[td=null,1]Text2[/td]
		[/tr]
	[/tbody]
[/table]

 

[Keiji]

I have now updated the BBcode guide to reflect the above changes, you can read further there for any assistance on bbcode if you need.
https://ninpocho.com/viewtopic.php?f=620&t=56030

I also managed to update the progress bar as I had been told that progress bar had broken. So now we're using the new html5 progress bar code and just altering the value in it with the content of the bbcode.
But on TOP of that! I also added the potential of adding a second variable which is text within the progress bar Took a little testing, but I got it to work! * (If you don't see it press ctrl+f5 (cmd+F5)
[progress]25[/progress]

* On a side note, I'm working on making the progress bar look alike on all browsers. As currently on Firefox and Internet Explorer(ha!) The text within the progress bars does not appear. And it looks substantially different too! So you need to right click "inspect" and read the "data-label" to actually see what people have written on the progress bar for those browsers. Hopefully I'll have a solution for that soon!

I'll continue to use this thread for now on all updates and changes that involve the update and complications/bugs there-in.

For those that don't know. If you experience any issues, bugs to report, or just need ideas, suggestions and coding help for your posts, profiles, training, etc. Please check up in our newly created Discord channel #bugs-and-styling down in the random section of our Discord server. I'm usually always around to help. If not, there's bound to be someone more familiar than me with our bbcode potential in there too.

 

[Keiji]

I've updated the bbcode guide to reflect the changes the creator of the table bbcode made recently that removed the linebreaks.
In order to add linebreaks you use a new bbcode called lb and lb2
One makes a simple linebreak, the other makes a double linebreak.

Just write the new bbcode in a line for itself.
The way it works, is by make a divbox that is either 1px high, and 12px high.
I chatted with the creator of the extension himself in order to figure out how to get it to work. So props for him at being socially available and awesome to help.

Examples:

[table=100,null]
	[tbody]
		[tr=bg2]
			[td=null,1]Lorem ipsum dolor sit amet, consectetur adipiscing elit.[lb][/lb]
Vestibulum tincidunt ultricies diam a pellentesque. Vestibulum eu viverra dui. Mauris consequat lobortis lorem nec scelerisque. Curabitur id ultricies turpis, vitae suscipit erat. Duis eu elit finibus, cursus urna eget, sollicitudin nibh.[lb2][/lb2]
Sed commodo dolor commodo, molestie nibh sit amet, scelerisque lectus.[/td]
		[/tr]
	[/tbody]
[/table]

Lorem ipsum dolor sit amet, consectetur adipiscing elit.[lb][/lb] Vestibulum tincidunt ultricies diam a pellentesque. Vestibulum eu viverra dui. Mauris consequat lobortis lorem nec scelerisque. Curabitur id ultricies turpis, vitae suscipit erat. Duis eu elit finibus, cursus urna eget, sollicitudin nibh.[lb2][/lb2] Sed commodo dolor commodo, molestie nibh sit amet, scelerisque lectus.

[tbody]

[/tbody]

And then without the line break code to see the difference.

[table=100,null]
	[tbody]
		[tr=bg2]
			[td=null,1]Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Vestibulum tincidunt ultricies diam a pellentesque. Vestibulum eu viverra dui. Mauris consequat lobortis lorem nec scelerisque. Curabitur id ultricies turpis, vitae suscipit erat. Duis eu elit finibus, cursus urna eget, sollicitudin nibh.
Sed commodo dolor commodo, molestie nibh sit amet, scelerisque lectus.[/td]
		[/tr]
	[/tbody]
[/table]

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum tincidunt ultricies diam a pellentesque. Vestibulum eu viverra dui. Mauris consequat lobortis lorem nec scelerisque. Curabitur id ultricies turpis, vitae suscipit erat. Duis eu elit finibus, cursus urna eget, sollicitudin nibh. Sed commodo dolor commodo, molestie nibh sit amet, scelerisque lectus.

[tbody]

[/tbody]