Welcome to the HornSports Forum

By registering with us, you'll be able to discuss, share and private message with other members of our Texas Longhorns message board community.

SignUp Now!

Problems with the Board?

tejasrulz

Well-known member
Joined
Oct 30, 2014
Messages
6,643
Anyone else having issues with this board? Nothing major but noticing different behavior with the notification button and when replying to a post.

 
I haven't experienced anything. It may be useful to Aaron and Co. if you list some more specifics. Like what device you're using, which browser and etc.

 
 

Anyone else having issues with this board? Nothing major but noticing different behavior with the notification button and when replying to a post.
 
Yeah, I'm getting some goofy script replying to your post. "&nbsp"?

I also tried unsuccessfully to change my signature and it didn't work. Something is up.

I'm using Chrome as my default browser. Never had a problem before like this.

 
Last edited by a moderator:
The page is now reloading if I "like" a comment. Also, the reply box has changed to a basic, text only option.

 
I use FireFox but just tried IE and get the same results.

For example, I click on my notifications and in the past it would take me to the post someone liked, now it just lists them.

When I reply, I get no way to add links, pictures, quotes or emoticons, etc. Now I can just enter plain text.

 
I use FireFox but just tried IE and get the same results.For example, I click on my notifications and in the past it would take me to the post someone liked, now it just lists them.When I reply, I get no way to add links, pictures, quotes or emoticons, etc. Now I can just enter plain text.
 
Mine too

 
Now that I'm thinking about it, I did have an issue with the "username" portion of a reply to a JB post this morning. I just deleted it. I had forgotten that until JB just mentioned it.

 
Last edited by a moderator:
Awesome! So I guess we can all agree to put &nbsp at the beginning of all of our posts until April Fools now right?

 
Yes

1. The ajax scripts are not working. Everything is a postback instead of asynch now.

2. The rich text box editors have been turned off

3. Double escaped html is appearing in posts probably because html editors have been turned off.

4. 19 script errors on this page alone.

Code:
ncaught TypeError: $(...).down is not a function(…)
Uncaught TypeError: $(...).down is not a function(…)
Uncaught TypeError: $(...).down is not a function(…)
Uncaught TypeError: $(...).down is not a function(…)
Uncaught TypeError: $(...).down is not a function(…)
A Parser-blocking, cross-origin script,  is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
Uncaught TypeError: $(...).getAttribute is not a function(…)
Uncaught TypeError: element.attachEvent is not a function(…)
Uncaught TypeError: element.attachEvent is not a function(…)
Uncaught TypeError: element.attachEvent is not a function(…)
Uncaught TypeError: $(...).getWidth is not a function(…)
Uncaught ReferenceError: hornsports is not defined(…)
Uncaught TypeError: element.dispatchEvent is not a function(…)
Navigated to http://www.hornsports.com/forums/index.php?app=forums&module=post&section=post&do=edit_post&f=14&t=13401&p=236547&page=
A Parser-blocking, cross-origin script, https://hsmain-hornsports.netdna-ssl.com/public/js/ips.quickpm.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
A Parser-blocking, cross-origin script, https://hsmain-hornsports.netdna-ssl.com/public/js/ips.hovercard.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
A Parser-blocking, cross-origin script, https://hsmain-hornsports.netdna-ssl.com/public/js/ips.post.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
A Parser-blocking, cross-origin script, https://hsmain-hornsports.netdna-ssl.com/public/js/ips.attach.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
A Parser-blocking, cross-origin script, https://hsmain-hornsports.netdna-ssl.com/public/js/ips.textEditor.bbcode.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
A Parser-blocking, cross-origin script, https://hsmain-hornsports.netdna-ssl.com/public/js/ips.textEditor.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
Uncaught ReferenceError: jquery is not defined(…)
A Parser-blocking, cross-origin script, http://www.googletagservices.com/tag/js/gpt.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
A Parser-blocking, cross-origin script, https://securepubads.g.doubleclick.net/gpt/pubads_impl_105.js?v=105, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
A Parser-blocking, cross-origin script, https://securepubads.g.doubleclick.net/gampad/ads?gdfp_req=1&correlator=367…05&vrp=105&ga_vid=322038873.1477493802&ga_sid=1480456146&ga_hid=1742090297, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
A Parser-blocking, cross-origin script, https://securepubads.g.doubleclick.net/gampad/ads?gdfp_req=1&correlator=367…05&vrp=105&ga_vid=322038873.1477493802&ga_sid=1480456146&ga_hid=1742090297, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
Uncaught TypeError: $(...).getAttribute is not a function(…)
Uncaught TypeError: element.attachEvent is not a function(…)
Uncaught TypeError: $(...).getWidth is not a function(…)
Uncaught ReferenceError: hornsports is not defined(…)
Uncaught TypeError: element.dispatchEvent is not a function(…)
'webkitAudioContext' is deprecated. Please use 'AudioContext' instead.
Uncaught TypeError: Cannot read property '1' of null(…)
 
Last edited by a moderator:
"We're aware and working on it. Thanks for your patience!"

Thanks Staff!

 
They do appear to be resolved now. Thanks for getting up on top of it!

55a489144aa2187609003947.jpg


 
Back
Top Bottom