Browser? Works on other browsers?
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial
Smart Tag Closer
Arantor
-
-
- As powerful as possible, as complex as necessary.
- Posts: 14,278
oOo--STAR--oOo
- @Arantor Our greatest weakness lies in giving up. The most certain way to succeed is always to try just one more time
- Posts: 43
Hold up.
Sorry I am using google chrome, maybe you have made some changes that require me to clear cache unless your using ?blah on the end of the links to your scripts/css
I tried to repeat it with [b]hello
Its not doing what it used to before.
As in closing the tag and opening a new one :S
Sorry about the not working statement.. Kinda dumb.
Sorry I am using google chrome, maybe you have made some changes that require me to clear cache unless your using ?blah on the end of the links to your scripts/css
I tried to repeat it with [b]hello
Its not doing what it used to before.
As in closing the tag and opening a new one :S
Sorry about the not working statement.. Kinda dumb.
Arantor
-
-
- As powerful as possible, as complex as necessary.
- Posts: 14,278
Please re-read the second post in this thread. It isn't designed to close that tag. It's designed to be used when you're *already inside a tag* to end it and start another one.
Like when you've quoted a post, you press-shift enter in the middle of it to close the existing tag, create a new opening tag after where you were, so you can reply to it in parts.
That said, it isn't working right now, though I figured that was due to my laptop having an odd keyboard.
Clearing the cache won't get you anywhere because the files are automatically compressed and they're given a new filename each time that's done so it shouldn't be caching anything because it's a physically different filename.
Like when you've quoted a post, you press-shift enter in the middle of it to close the existing tag, create a new opening tag after where you were, so you can reply to it in parts.
That said, it isn't working right now, though I figured that was due to my laptop having an odd keyboard.
Clearing the cache won't get you anywhere because the files are automatically compressed and they're given a new filename each time that's done so it shouldn't be caching anything because it's a physically different filename.
oOo--STAR--oOo
- @Arantor Our greatest weakness lies in giving up. The most certain way to succeed is always to try just one more time
- Posts: 43
Alright, no problem man.. I understood the 2nd post.
Also you may already know / use this but have you looked at google developers?
https://developers.google.com/pagespeed/#url=wedge.org&mobile=false
I see you have got almost everything covered here XD compared to mine anyway LOL.
Helps a lot when designing, a night mare on something already fully running and full of manual rubbish lol.
Also you may already know / use this but have you looked at google developers?
https://developers.google.com/pagespeed/#url=wedge.org&mobile=false
I see you have got almost everything covered here XD compared to mine anyway LOL.
Helps a lot when designing, a night mare on something already fully running and full of manual rubbish lol.
Nao
- Dadman with a boy
-
-
- Posts: 16,082
Also you may already know / use this but have you looked at google developers?
https://developers.google.com/pagespeed/#url=wedge.org&mobile=false
Well, some of their remaining hints are things I can't deal with, such as compressing another item by 200 bytes... They're nice but I can't. What they're actually suggesting, is removing the copyright comments and recompressing it.
Or that hint about no longer executing jQuery... :) That only costs us a point at worst though, and saves us another 10 or 20 just by reducing the overall size of the whole page.
Oh, a fixed bug... Gone to archived now, gone.