....I'm so lost now..

[Kami]

Okay, they DO work, first of all. They just don't work in the manner you're expecting. See the difference? You don't need the style UBBC / enhanced tables because PB now supports div styling, which means you can do practically everything you did with those codes already hard-wired into PB's system.

Now, the first problem with your statement is the fact that you were using a third-party code. While I understand your frustration, that code was a workaround based on the limitations of the v4, v4.5 software. With divs and div styling already hard-coded, it would be absolutely redundant to create two plugins to re-use outdated workarounds, simply because you don't want to update [atrb=border,0,true] to [div style="border: none;"] or whatever it happens to be now.

If how many users are using a same format with something, and suddenly that format breaks, you fix it; not force hundreds of users to re-write everything.

I definitely understand your frustration with that. I'm not looking forward to recoding my templates myself. But that's the risk you take when you use a third party code - codes become obsolete. You're essentially asking for a downgrade with these codes. =/ While I expect that it's not impossible to do (I'm not a coder so I wouldn't say for sure) I don't know how many people would be willing to format a code that works around things you no longer need to work around.

I could even be snooty and say something asinine like "oh, well if they are already incorporated then how about /you/ go fix all these 1000+ templates for me and all others that are asking for the plugin."

Considering the fact that you DID say that instead of keep it to yourself, you are being snooty, and I fail to see how that's going to help you solve anything. I was just letting you know that these codes are not needed anymore, and the attitude is really a deterrent from me ever replying to your threads again.

[Shrike]

Although I haven't tried it myself (mainly because I've not used the style tags before), but you could probably convert a lot of the old [style=""][/style] tags into the native [div style=""][/div] tags using the censored words feature. I might look into it at some point over the Christmas break, but the [attrb] ones could probably also be converted somehow.

At any rate, it's definitely much better to start using the new tags because they don't need any other code to make them work, they'll already be understood by your browser.

[Tohsaka Rin]

There is no way that I can change everything to using divs when its way over 1000+ templates, of which are not just my own but many that were requested (and paid for) by many other websites using my designs. Heck, I don't even think that a lot of the code parts themselves are even capable of being used in a div tag.

I don't even know how to code divs in the first place, I was lucky with just getting by using what I could with the style tags. Someone would have to remake every single one of my templates for me, and not just me, but all those other sites and people that have the same issue which requested (and paid for) my help.

/That/ is the huge problem.

[Tohsaka Rin]

Dec 9, 2012 16:45:01 GMT -8 Shrike said:

Although I haven't tried it myself (mainly because I've not used the style tags before), but you could probably convert a lot of the old [style=""][/style] tags into the native [div style=""][/div] tags using the censored words feature. I might look into it at some point over the Christmas break, but the [attrb] ones could probably also be converted somehow.

At any rate, it's definitely much better to start using the new tags because they don't need any other code to make them work, they'll already be understood by your browser.

Nope, doesn't work. I already tired it and it utterly fails with being able to convert anything correctly. It just ends up garbled code like before.

A lot of it is also due to the attribute area not being able to function either.

Converting them would save so much time as I have way over 3000 thread posts just on my site that use them. I can't even think about going back and manually changing every single one; especially since mine is not the only site that uses them heavily.

[Shrike]

Dec 9, 2012 16:47:18 GMT -8 Tohsaka Rin said:

There is no way that I can change everything to using divs when its way over 1000+ templates, of which are not just my own but many that were requested (and paid for) by many other websites using my designs. Heck, I don't even think that a lot of the code parts themselves are even capable of being used in a div tag.

I don't even know how to code divs in the first place, I was lucky with just getting by using what I could with the style tags. Someone would have to remake every single one of my templates for me, and not just me, but all those other sites and people that have the same issue which requested (and paid for) my help.

/That/ is the huge problem.

Can you post an example of one of these style tags? From what little I have seen, I'm pretty sure that one of the codes for them actually converts them to divs with a style attribute: exactly what you can do natively with V5.

I knew there were two things that lots of people would be irritated about them not working: UBBC style tags and the MYO profile/board mods. These are both as easy (if not more so, especially for the MYO mods) as before to work in V5 except now they're much faster because they're being done natively. The only problem is the conversion.

[Kami]

Dec 9, 2012 16:47:18 GMT -8 Tohsaka Rin said:

There is no way that I can change everything to using divs when its way over 1000+ templates, of which are not just my own but many that were requested (and paid for) by many other websites using my designs. Heck, I don't even think that a lot of the code parts themselves are even capable of being used in a div tag.

I don't even know how to code divs in the first place, I was lucky with just getting by using what I could with the style tags. Someone would have to remake every single one of my templates for me, and not just me, but all those other sites and people that have the same issue which requested (and paid for) my help.

/That/ is the huge problem.

Even so, you are still asking for a workaround to be implemented when a workaround is no longer needed. Does that make sense? Basically, the style tags and enhanced UBBC codes used javascript to allow you to use HTML, which is what divs and div styling are. So, you're asking for an updated version of a code that is no longer necessary because you are directly able to accomplish this, just in a different way.

I have used iPokemon's style tags code and they DO use div styles - at least, the updated version currently uses them. So I'm not sure why those wouldn't work. It would depend on how you have it structured. As far as the enhanced tables UBBC, which is probably what the biggest issue is, I really don't know what to say that I haven't already said about you asking for an update to a code that works around things that no longer exist.

[Tohsaka Rin]

This is a quick example of one, I won't post another since they are way too huge. A few links will be provided between V4 and V5 to show them. Two people already tried converting some over and it really just does not work, which in my opinion it just seems so... backwards.

• User Posting Template (updated to better links)
  
  1. V4: [Here]
     
  2. V5: [Here]
     
  
  
• News Template:
  1. V4: [Here]
     
  2. V5: [Here]
     
  
  
• Large conglomeration of tables/styles:
  1. V4: [Here]
     
  2. V5: [Here]

  
  

• Request Example:
  1. V4: [Here]
  2. V5: [Here]

  
  

- There was no way to post the code template in without it causing issues to this thread; thus I had to remove it and opt for just posting links in.

Those are just on my site, and just a few; not even going to include all the other sites using similar ones I coded for them.

---

We shall do some math here:
On my site alone I have anywhere between 40-50 active members, of which post "at least" once a week (to which each use their templates) on a site that has been around for 2 years.

I will be kind and just do the most minimum equation of how many templates would have to be fixed just on one site alone:

40 (members posting once per week)x4 (weeks a month)x 12 (months a year) x2 (years) = 3840 templates that must be fixed.

- 3840 posts using templates out of 4,526 posts total; and that is well over 80% of the forum being posts using posting templates alone! The remaining 686 posts still may/may not contain posting templates because they are things like the newsletter, mission posters, character tables... and whatnot.

Most of said templates were paid for, basic posting templates were anywhere between $5 and $10 dollars depending on how much art I had to make for them; templates such as the newsletter were $25 dollars.

A lot of these roleplay sites have been using templates they either won, purchased, or commissioned from me...scaling far over 3840 on (just on one site) of posts that would have to be all remade.

[Kami]

We can't see the first without logging in, do you perhaps have a test forum?

Also, I know for a fact that you can use the codes from iPokemon's style tags code on v5, since I just did. That section allows for guest posting, so feel free to quote that post and see how it's done.

Now, I can't load everything you've linked to (my internet is really lousy tonight), but I managed to see at least one of the issues. Right now you have:

[style=margin-left: 0px; margin-right: 0px; margin-top: -35px; margin-bottom: 5px; width: 552px; border: 1px solid #aa975c; text-align: justify; padding-left: 5px; padding-right: 5px; padding-top: 5px; padding-bottom: 5px; opacity: .8; border-radius: 2px; -moz-border-radius: 2px;]October 2012[/style]

This tells me that (a) you're not using the updated version of iPokemon's style code, which I really recommend as it fixes security issues (it comes with an auto-converter to fix those tags for you, you'll have to click "modify" on all posts and press the "convert" button, however), and (b) that if you want to use Shrike's censored words workaround, you'll need to turn whole words censors OFF, and censor:

[style=
to
[div style=" 


;]
to
;"]

and
[/style]

to
[/div].

[Tohsaka Rin]

IF it is possible to use Shrike's recommendation of swapping censors around, that saves a lot of time, but won't really fix the issue with attributes that do not yet exist within the expanded table code of V5...

[Kami]

Dec 9, 2012 17:37:36 GMT -8 Tohsaka Rin said:

IF it is possible to use Shrike's recommendation of swapping censors around, that saves a lot of time, but won't really fix the issue with attributes that do not yet exist within the expanded table code of V5...

You're right, it doesn't.

That's mainly because (a) [atrb=] / [cs=3] ubbc is non-existent, and (b) you use style tags within the table options now. A plain table in v5 that looks like this:

Row 1 column 1	Row 1 column 2
Row 2 column 1	Row 2 column 2

looks like this using UBBC:

[table][tbody][tr][td style="border:1px solid #000;padding:3px;"]Row 1 column 1[/td][td style="border:1px solid #000;padding:3px;"]Row 1 column 2[/td][/tr][tr][td style="border:1px solid #000;padding:3px;"]Row 2 column 1[/td][td style="border:1px solid #000;padding:3px;"]Row 2 column 2[/td][/tr][/tbody][/table]

So, basically, you'd have to fix a handful of things with the enhanced table codes.

1. Change any of your [cs=x] tags to proper [td colspan="x"] (so, for instance, if your tag says [cs=3]some text here, change that to [td colspan="3"]some text here[/td]. Don't forget to CLOSE the colspan td, since that is not something you do in the enhanced UBBC table code (remember: these are FAKE tags in the enhanced code designed to mimic real tags). The same thing if you have a rowspan, though I don't remember what the enhanced ubbc tag is (rs, perhaps?).

example:

column span
Row 1 column 1	Row 1 column 2
Row 2 column 1	Row 2 column 2

2. figure out how to assign the atrb tags properly. If you want the width of the table a certain size, instead of saying [atrb=width,600,true], you can input it via "table width="XXpx;", like so:
[table width="600px;"]

Using the above table as an example:

[table width="600px;"][tbody][tr][td style="border:1px solid #000;padding:3px;"]Row 1 column 1[/td][td style="border:1px solid #000;padding:3px;"]Row 1 column 2[/td][/tr][tr][td style="border:1px solid #000;padding:3px;"]Row 2 column 1[/td][td style="border:1px solid #000;padding:3px;"]Row 2 column 2[/td][/tr][/tbody][/table]

yields:

Row 1 column 1	Row 1 column 2
Row 2 column 1	Row 2 column 2

I doubt there will be a quick fix for this, but it's not as complicated as it looks - just time consuming.

EDIT: it looks like width settings only function in the visual preview / thread summary and not the actual post, which might be a bug.

[Kami]

Good luck, but I seriously doubt anyone will recode the current codes when the functionality already exists in v5. You might be better off asking for a code or plugin to help find any old style/enhanced UBBC tags within posts and convert them to the current UBBC, rather than re-creating the v4 codes.

[Tohsaka Rin]

Dec 9, 2012 19:41:19 GMT -8 Kami said:

Good luck, but I seriously doubt anyone will recode the current codes when the functionality already exists in v5. You might be better off asking for a code or plugin to help find any old style/enhanced UBBC tags within posts and convert them to the current UBBC, rather than re-creating the v4 codes.

That was sort of what I was aiming for; a conversion plugin.

[Kami]

Dec 9, 2012 19:58:17 GMT -8 Tohsaka Rin said:

Dec 9, 2012 19:41:19 GMT -8 Kami said:

Good luck, but I seriously doubt anyone will recode the current codes when the functionality already exists in v5. You might be better off asking for a code or plugin to help find any old style/enhanced UBBC tags within posts and convert them to the current UBBC, rather than re-creating the v4 codes.

That was sort of what I was aiming for.

Fair enough. It sounded like you wanted it the other way around (making the workaround tags the default / remaking the code so that the default ones are still "valid"), rather than editing the current bits.

[Tohsaka Rin]

Yes, I just want a simple conversion plugin that will swap the stuff over so that it doesn't need to be done manually.

It's hard to not sound all upset when typing out explanations on some of this.

In essence, it would be similar to the ability to swap it over using the censors, but it would be best to just have it set as a plugin to convert them (as it would do it all at once and can include all the broken table attributes that are not yet included in the new table conversions for V5.)

Having a plugin convert it saves hundreds of forum owners all that time... I would actually flip a lid if I was told I had to manually edit over 3K+ threads individually just to do it.

.....just thinking about it makes me want to flip a table.

[Kami]

I guess I just want to emphasise that the "broken table attributes" will not (well, in all likelihood. I'm not a developer for PB) be included in v5 because they're not real attributes. Like, [cs=2] is not a real attribute, so it's not going to be added (or rather, is already there via proper UBBC [td colspan="2"]). I just don't want you to expect them to be added to v5.

The biggest issues I can see with getting a conversion plugin/code (and again, I'm not a coder so I'm not 100% sure about this) are (a) that the cs & atrb tags aren't full tags. Like, there's no ending tag like [atrb=whatever][/atrb], it's just a singular opening tag with no content and no indication of where the styling should end; and (b) that the atrb tag is incredibly varied in what it can do. Like, the reason it'd be difficult with censored words is that you'd literally have to censor EVERY instance and variation of the tag, which I can imagine is similar to what any conversion code/plugin would also need to do.