camelFun

kill yourself canadian bill you false flagging nugget fugger

kill yourself canadian bill you false flagging nugget fugger

@CanadianBill FUCK OFF YOUR DUMB
 

Well spent <3. 

I see that Timmy Jimmy you got goin there.

I see that Timmy Jimmy you got goin there.

ayyy
 

Probably won't make one

4.1.9 will be applied shortly. Here is the changelog of the newest version for your reading pleasure: 
 
New or Changed Features
When your link auto-embeds in a post such as with an image, YouTube video, Twitter link, etc. an option will now display to revert the embed back to a plain text link if you do not want the embed. New setting to disable embedding. Facebook/Twitter integration improvements If you are an administrator and encounter a system error, additional debug output will now display. Regular members will see the normal error message. Custom Fields for Support Requests in Commerce now show on the front-end. If an advertisement is set up with a main image, but not smaller images for tablets/mobiles, the ad would not show at all on tablets/mobiles. This has changed so the main image will display on all devices unless smaller images are provided. Topics scheduled to automatically lock or unlock will now reflect this in the topic listing and when viewing the topic. Placing a link to a Facebook status will embed when possible. When viewing a report, the container (for example, the forum) the content is from is displayed. Three character searches are now allowed in the Admin CP Live Search. The Account Settings page now uses vertical rather than horizontal tabs to prevent overflow. If Gravatar is enabled, and a user has not defined an profile photo, then their email address will be used to fetch from Gravatar unless explicitly set not to. Gfycat embeds now use their oEmbed endpoint rather than their JS API. Using Amazon CloudFront as https provider will now be recognized as valid secure connection. The member REST API endpoint will now return custom fields. The Developer Center for Plugins now shows the filename in the list of hooks, and when editing a hook, a breadcrumb includes a link back to the list. Inline notifications can now be dismissed Efficiency improvements to the search index You can now close a poll independently of the topic
  Important Fixes
In addition to dozens of smaller fixes this release includes fixes for the follow items that impacted many clients: Several security enhancements. The posting parser has been made more efficient. Some BBCode does not parse correctly in version 4 and we have applied some fixes for this. In general BBCode is deprecated so we only provide basic support. Sitemaps could sometimes be blank if there was no content in a specific section. Certain URLs from version 3 were not redirecting properly to the new version 4 format. The timezone detection is now more robust and will more gracefully fail if it cannot determine a visitor's timezone. Permission matrices have been reworked to send less data to prevent exceeding server limitations. Decimal handling has been reworked in Commerce for more precise calculations. The database class now handles InnoDB deadlocks more gracefully, and some queries have been changed to reduce the likeliness of deadlocks. Performance improvements to areas which perform large updates on the members table (for example, when editing permissions). Pages 'number' custom fields previously had an upper limit for submitted values around 2 billion. Multiple fixes for tag searching

Huh.. Never noticed that. Just fixed it.

Huh.. Never noticed that. Just fixed it.

Huh.. Never noticed that. Just fixed it.

Huh.. Never noticed that. Just fixed it.

Huh.. Never noticed that. Just fixed it.

So there is this thing called "parsing", which means that, in this case, a string of characters is being analyzed and compared. So while BBCode is still "supported," it isn't done in the conventional way. The entire backend for the editor is HTML now, not BBCode. So while you can still use BBCode, it isn't a BBCode backend. So what is actually happening is: Before a post is made, when the editor reads a BBCode tag, such as [img\], it will parse the contents and translate them into the HTML backend. i.e:
 
 
[img=www.ayylmao.com/aliens.jpg]    
^ That will be parsed and translated into:
 
 
<img src="www.ayylmao.com/aliens.jpg">    
A BBCode backend works the same way, only in every post, those BBCode tags are retained. The only reason you can still use any BBCode now is because people adapt so poorly to change, so the Invision Power guys decided to make a legacy system for those of you who don't want to change.
 
In the current, modern editor, everything is there for you in the form of the buttons. If you want to see or change the text or URL in a link, just click on the link in your post and click the Hyperlink button. That was already a function since before 2005, only using a BBCode backend, but since you don't actually use the tags manually now I can see how you might have overlooked it.
 
Either way, this is how it is now. It's much more efficient, and not ancient

 
There's no other way to allow you to embed an imgur webm without giving you full access to certain html features that would allow you to post screamers. Sorry, my ears > your privs.
 
btw, several people in this thread didn't have issues using basic forum functionalities, idk man

you guys can add a clamps button but not (img)(/img) tags?
or webms that play auto muted? you guys need to set your priorities straight and trust the community a little more than nothing. 

If non-staff had html privileges we'd have screamers in every single thread.

If non-staff had html privileges we'd have screamers in every single thread.

 
It's a font family.
 
And I thought users couldn't use Subway.
 
There is nothing to fix this. You're logging onto your account on a different device which will use the default color scheme due to, what you say are, the limitations of the theme (I'll check it out). It's not a bug since that information is saved in the ipsregistry I'm pretty sure, connected to your account.
 
EDIT: Yeah, definitely a decision made by the theme designer. Not a bug and nothing we can do about it.

All of our PHP pages are broken due to the new way IPB handles PHP in the Pages application. I went ahead and edited everything for the credits claim page to work with the new system. Tested it on myself, works fine. You should be good to go. Please let me know in this thread if all works out for you.
 
http://www.joinsg.net/credits_claim_page.html/

All of our PHP pages are broken due to the new way IPB handles PHP in the Pages application. I went ahead and edited everything for the credits claim page to work with the new system. Tested it on myself, works fine. You should be good to go. Please let me know in this thread if all works out for you.
 
http://www.joinsg.net/credits_claim_page.html/