Wedge

No, no...
They won't compress a gz file. They have that extension. Why would they compress them again..?

Also, compressing a file by default doesn't mean it's not cached anywhere. Meaning there's a chance it'll have to recompress all of these files on every page load. One of the reasons I wrote this feature was to get rid of one of my servers' tendency to waste time on this.

Thanks!
I don't know if Pete is happy about this public release, though... It's a major competitor for him, and it will now be a bit more obvious that whatever "innovation" he's implementing in SMF, actually was implemented in Wedge years ago. (Thankfully, he's mostly re-implementing his own old things, and leaving mine mostly alone. I don't think he wants to risk breaching the license agreement. I would hope that he doesn't want to risk it, at least.)I still have a huge to-do list, anyone willing to help on trimming down that one is welcome, but I have to do something and build a 'to do' board, or open github issues about them, I don't know... :^^;:

View source code in Chrome Mobile: open the URL bar, go to the beginning, and add view-source: to it. Thanks to backwards compatibility, you can't get away with just 'source:'. No, you have to frigging type a long text, and switch keyboard modes 4 times (instead of just once) to find the '-' and ':'. Thank you, Google... :P Or they could just add a View Source menu item if Developer mode is active, of course...

Also, ffio.it is working just fine for me..?! (Apart from JS being disabled because you're on that frigging Google CDN, of course. I may start considering going to the jQuery CDN by default... :lol:)

I don't underestimate your skills. To be specific, I underestimated your skills for a long time because you didn't show them off, but you've seen proved that you can be very dedicated to your current task (if anything, the German translation is nothing short of impressive -- you pulled it off from scratch in a couple of weeks, IIRC..?), I just wasn't aware until recently that you had programming skills. Just call it 'ignorance' from me, I think it's neither more nor less than that. ;)

As for the ad management plugin, perhaps we could both work on it, under the Wedge Team flag. (i.e., a 'wedge:ads' plugin.) Maintain it on Bitbucket together in a private repo, and then when we're happy with it, either release it for free, or do something related to member groups.

Re: your PMs, I'm just at a loss right now... :whistle: I need some time to answer them. (Plus all of the other outstanding PMs I have.)

First, let me reproduce your bug...


Hmm. That's unsettling. I'll look into it when I have more time. This is one of the usual 'bugs' in BBC parsing in SMF and forks, BTW. I've fixed this kind of bug many times. It pretty much warrants a rewrite of the protection code, but parse_bbc is a behemoth that no one likes, but still is more efficient than early SMF 1.0 regex versions.

Now, when it comes to iframes, I would recommend that you use the current code in the YouTube embed array. It's more solid, because it's responsive. Then, come back to me. ;)

It's a problem I've been aware of for years, but Google never let me down for more than a few seconds, and I didn't expect they'd take so long to update their links. (See New Revs for a fix.)

The only 'sure-fire' solution is the widely documented <script> hack right after the CDN link. For instance, ElkArte implemented it (look at their source code, more particularly window.jQuery || document.write...)
The problem is, this adds over a hundred bytes to all pages. It's acceptable, but not something I'm looking forward to doing, especially given that Google never let me down until now. So, to me, it's been a bit of a waste of space...
Additionally, Wedge can't link directly to the jQuery files, because they're protected by htaccess. I used to do that to prevent people from looking into my JS code while the Wedge source code was heavily guarded, but it's no longer a problem. However, I could imagine that some people might want to write some extra scripts and hide them from view, and thus might enjoy this htaccess file too. (If they're writing a plugin, they can always take that file and put them into their own plugin folder, it should work the same.)
So, that would force me to do a 'dummy' gz version of the jQuery files, which is fine by me, but not yet implemented, ah ah. (Because JS files are only gzipped as they're requested, and when using a CDN, the local jQuery is obviously never requested.)

I've never experienced this, and I wrote the whole thing.

Wuthering specifies Wine as its parent in the skin.xml file.
Wedge builds a chain of nested skins (Weaving < Wine < Wuthering), and then proceeds to load the CSS in order (Wuthering in last, then.)
If you can't override a setting from Wine, you may have done it incorrectly.

The first thing to test is using the reset keyword. Just add it to a selector you want to restyle from scratch. Just use #linktree reset instead of #linktree if you're about to overwrite the linktree. Ensure that you copy all CSS you want to keep from the parents, of course. 'reset' will delete *any* CSS declarations prior to the one found in that place, so even declarations found within the same extra.css file will be erased if they're made before. All right..?

Then, there's the order in which files are loaded. 'extra.css' comes after 'index.css' and 'sections.css', so it should override anything in those, regardless of whether they're in Weaving, Wine or your own skin. So, normally you've got everything covered here.

- I did say in the New Revs topic (which I expect everyone to read, *at least the grayed out comments* except for new installers), that I had updated jQuery to 2.1, and that it wasn't available yet on Google. What I didn't expect was for Google to STILL not have it up two days later (when it's happily available on the jQuery and Microsoft CDNs.) It's too long a time, and means every new install of Wedge breaks. I'll have to revert this for the time being. (Next commit.)

- This can be due to many things. What do you get when you click the css.gz links directly?