Yep, that is the first issue that has been going on. If you go in to Plugins>Build and try to edit the css area it 99% of the time breaks the entire plugin and you have to remove it, and all data, and put it back in before it works again. Which means you are back at square one and have to try all over again.
I actually had to give admin access to my friend that was trying to help work on it, and let me tell you, I do /not/ like having to give my account information to someone just because proboards will not allow us to add who can modify what plugins.
Not happy with that one bit.
After we had injected a bunch of stupid hacks into the code, because directly writing to the css breaks the entire thing, the gradient above "Home" in my welcometable shows up as having a gray line and a black line above and below it. It was not there prior to us trying to fix the DTT... and we have no idea how to remove it. The gradients for all that stuff should have been removed ages ago and so I do not know why, or how, to remove it since it is "already removed" supposedly.
Oh, right.. and about removing gradients for all you people wondering... IT SCREWS UP YOUR WHOLE FORUM!!!!!
(Please see reason I bring this up below~)
If you remove the gradient from ANY of the header/title containers, WHATSOEVER, you are left with a hideous mess of 10px padding gaps between crap... something proboards apparently did not foresee happening or have a remedy to fix in any way unless you cut their entire code apart with a weed-wacker. WHY DID THEY DO THIS? Don't ask me... le sigh~
^-_-'^
And it is messing with css functions on trying to move the DTT where we want it because it is causing a padding issue where we cannot move the DTT into the proper area since that gradient is causing a buffered zone.
I never had a problem working with the V4 version but this is the stuff of nightmares. We keep having to put in injector hacks, so far we are up to five now, just to fix a lot of this.
There is also an issue with how the values are named, because they often have the same names as a lot of the values currently being used by the forum itself. Aka, when we put in the hack for allowing an image in the header area it caused this 10px empty space separating the actual header image and the content box.
The value of the content box is the same value as the name of the forums.
So when we had the issue of putting an image into the category headers for the forums it caused a 10px space between the category header and the actual forum list container. We solved that with another stupid injector hack because apparently proboards had no ability to forsee that "hey people want to put images into the category headers instead of text, whoops maybe we should fix the padding issues it causes." Nope, they won't answer/help/fix any of that and so I went like three months bashing my head into the wall trying to figure out how to fix THAT issue.
However, it caused yet another issue, since the container for the DTT area has the same value of the forum container, once we fixed the padding issue caused by the category head images and put in the inject for the title image for DTT... the spacing issue for the DTT container ended up THE SAME AS the forum container issue mentioned previously.
To add more insult to injury... you cannot fix one.. without screwing up the other.
Thus, when we fixed the padding for the Category/Forum area to not have that 10px gap we could NOT fix the DTT title/container gap.....and vice versus...
........unless we put in yet another injector hack.... because we cannot edit the css without the whole plugin crashing and loosing all our work.
^@,@^.
We even tried to remake the plugin entirely from scratch but well my friend does not know any proboards values and has no idea how the plugin system works so anything he would make sort of.... ruins proboards as a whole and disables all plugins. Ahahahaha...
Course, this ALL COULD HAVE BEEN FIXED if we had access to the global CSS; but no, they won't let us do that since the first thing people will remove is the advertisements.
^-_-'^
So any fix we do ONLY ends up applying to ONE darn skin and if you have more skins you need to apply all this same crap to every other skin thereafter because proboards did not even put in the ability to "use for all skins?" option. Which, may I add, seems to be a lack of hindsight on this sort of problem.
In total, with the number of injections we had to do, and all the custom template bullcrud having to be moved around it is going to be a total and utter nightmare to make any other skins because there is no cascading style sheet that can be applied for "ALL SKINS"... like a global one, due to every single custom snipet someone puts in atop of any skin colours... so you would have to still manually go in and edit either all the stuff you want custom OR all the colour/content values.... which just means more and more work rather than an easier resolve.
^-_-'^
Man, why do my threads always sound so peevish... sorry. I use to work with a lot of programmers, and do programming back in the day till I gave up out of sheer frustration of other people's work. Normally companies make poor choices about something and it screws over like.. 90% of their customer base.. even when I had some professional coders take a look at this they went "WHY DID PROBOARDS DO THIS?!!!" and bash their heads on the wall.
....which made them not want to work with it in the first place.
All I could do was give them a shrug and tell them about the style-tag issue and they gripped their stomachs in pain and bashed their heads on the wall further.
It was pretty funny..... for like 5 minutes until we were still stuck with the problem of making the DTT a "crack-addict" script.
<T^T>
Poor script...
If only it let us modify the darn CSS in the first place....
<TAT>
With love,
~Rin
