Why does this site(the forum) load laggy and roughly? I use my PC with linux and firefox and it is bad. I don't know alot about Web development, but it seems to me that you are not implementing javascript right. Maybe you should do more CSS instead?
Are you having issues with the speed of the download of the page, or is the actual rendering time slow for you?
The site is pretty good for me, with the exception of the front page just because there are so many devices listed.
mine is speed, and also sometimes it freezes for a split second before loading the site.
It's the actual rendering of the page. It can be very bad.
Loads of desktop browser problems for me this morning.
I cannot delete a private message, so keep getting the annoying popup any time I click on a link.
One thread in Samsung Galaxy Note Dev section keeps producing
"Sorry, we encountered an error processing your request. Please go back and retry or wait a minute.
The Administrators have been notified of this error"
The threads don't update to bold script when something new's been posted.
Same here...
* User CP > list subscriptions are 'stuck' (not updating)
* Clicking on certain threads result in "Sorry, we encountered an error processing our request. Please go back and retry or wait a minute. The Administrators have been notified of this error"
* Threads in general don't appear to be updating with latest comments when in the 'forums>threads view'
edit- Forgot to add.. I can't quote people in responses either... when clicking on quote it takes me to the reply window without the message being quoted
Related
I tried to log on to xda this morning using chrome and received a Malware warning.
"www.xda-developers.com contains malware. Your computer might catch a virus if you visit this site."
Its not recived on the home page or the forums but only any page located above http://www.xda-developers.com/android/
my browser has no problem with
http://www.xda-developers.com/windows-mobile
Whats going on?
there was an attack on the site I think, at least I got redirected to a malware site once when I clicked page2 on the android news section, but afaik it's all gone now
check this link, should explain all: http://forum.xda-developers.com/showthread.php?t=854561
me 2
Firefox 4.0 beta 7 also gives me a warning.
The main site, http://www.xda-developers.com/ is ok to view, but http://www.xda-developers.com/android/the-weekly-qa-week-16/ gets blocked right away.
WTF?
The site admins are aware, and steps are being taken to get the warnings removed, now the infection is gone.
I think there is a bug in the Windows Phone IE implementation.
Even on my Focus I had tabs simply go blank while I was reading them or after I opened them but before I got to read them. It wasn't repeatable until now. Previously I reopened the same article a second time and it was usually fine. The reason it is so problematic is the way I read articles. I have an igoogle page full of RSS feeds from the top two dozen sites I follow. I skim the igoogle page and open the first five articles I want to read in other tabs, then I go back and read them one at a time. I would read engadget or gizmodo similarly. If the articles span multiple pages then I when click the "next button" I switch tabs to another article while the page loads. Maybe it is obvious to everyone but I do it this way so I don't have to wait for pages to load. Also I have my internet website settings on my phone set to desktop preference rather than mobile.
Anyway, the fact that the pages would go blank was most annoying because when I opened a tab that went blank I would have to go back through the original list of articles to figure out which one I had missed.
I couldn't duplicate it until I tried to read this article:
http://www.pheedcontent.com/click.phdo?i=d3debfc5accaa909f0cd201b356bfdc0
The article is pretty interesting - it is Tom's Hardware take on the new Intel Z77 chipset and Lucidlogix implementation. I would appreciate if anyone would try to read it for me. You will have to set your browser preference on the 900 to "desktop version" to duplicate the bug. I can sometimes get two or three pages in clicking 'next' before it crashes in one way or another. If nobody can duplicate my problem then my Lumia is going back for another 900.
Brought me to m.tomshardware.com for an article called "Intel’s Z77 Express And Lucidlogix MVP: New Features For Gamers - Z77 Express: USB 3.0 And Enhanced Manageability" with no problems...
Sent from my Lumia 900 using Board Express
-----
Update: So then I went back and opened the link with the browser in desktop mode and was able to get it to crash around the 4th page. However... I saw some funky rendering on the 3rd page so I'm not sure what caused the crash (could have been bad code from the article's site not handled well in IE).
Bug Submitted
eknutson said:
...was able to get it to crash around the 4th page. However... I saw some funky rendering on the 3rd page so I'm not sure what caused the crash (could have been bad code from the article's site not handled well in IE).
Click to expand...
Click to collapse
Thanks. I have submitted this as a bug. I am surprised that more people haven't commented on "desktop version" crashes in Windows Phone Internet Explorer. Maybe I should switch back to "mobile version" since most sites are now coded correctly for that.
Hi,
I use a lot the small arrow to the left of each subscribed thread to jump to the 1st unread post.
Most of the time it works correctly, but from time to time it will show me the start of the previous page and be left at the top, since the URL anchor is not present on that page.
The original link will be something like ".../showthread.php?goto=newpost&t=nnnnnn", which later resolves to ".../showthread.php?p=mmmmmm#postmmmmmm".
The problem is that "showthread.php", when processing with the "p=..." argument, sometimes fails and presents the previous page than it should. If I were to replace "p=mmmm" by "t=nnnn&page=yyy", leaving the anchor, it will work.
Based on some experiments, my guess is that that php, when processing in the p= mode, fails to handle the edge case where post_count mod page_length is 0. I tried it with multiple page sizes, and for the case I was trying it (before I read the post and now need to wait for another case like this), the post was a multiple of 10, 20, 30 and 40 but not 50. So, only after changing the page length to all values to confirm it was failing, and finally to 50, did it work properly.
I normally use 20 posts per page so the chances of the last unread being a multiple of that are pretty slim, but those using 10/page are likely to experience this more often.
FIX: The formula for the page count "page_number=((post_count - 1) DIV page_length) + 1" or equivalent. Currently there's an offset of 1 that probably nobody ever complained about (at least I didn't find any post mentioning this).
This occurs regardless of the selected theme, and also on the XDA app (the server side is probably the same, or shares that part of the code).
EDIT: It appears that the conditions are not that simple. Sometimes, *after* the situation has been triggered (or so it seems), refresh of the subscribed threads view won't solve it immediately. Even if my next unread post is, say, the 3rd on the next page, I'll still be taken to the top of the previous page and therefore not land on the right post (correct anchor, but wrong page). Something to do with caching, perhaps?
Tungstwenty said:
Hi,
I use a lot the small arrow to the left of each subscribed thread to jump to the 1st unread post.
Most of the time it works correctly, but from time to time it will show me the start of the previous page and be left at the top, since the URL anchor is not present on that page.
The original link will be something like ".../showthread.php?goto=newpost&t=nnnnnn", which later resolves to ".../showthread.php?p=mmmmmm#postmmmmmm".
The problem is that "showthread.php", when processing with the "p=..." argument, sometimes fails and presents the previous page than it should. If I were to replace "p=mmmm" by "t=nnnn&page=yyy", leaving the anchor, it will work.
Based on some experiments, my guess is that that php, when processing in the p= mode, fails to handle the edge case where post_count mod page_length is 0. I tried it with multiple page sizes, and for the case I was trying it (before I read the post and now need to wait for another case like this), the post was a multiple of 10, 20, 30 and 40 but not 50. So, only after changing the page length to all values to confirm it was failing, and finally to 50, did it work properly.
I normally use 20 posts per page so the chances of the last unread being a multiple of that are pretty slim, but those using 10/page are likely to experience this more often.
FIX: The formula for the page count "page_number=((post_count - 1) DIV page_length) + 1" or equivalent. Currently there's an offset of 1 that probably nobody ever complained about (at least I didn't find any post mentioning this).
This occurs regardless of the selected theme, and also on the XDA app (the server side is probably the same, or shares that part of the code).
EDIT: It appears that the conditions are not that simple. Sometimes, *after* the situation has been triggered (or so it seems), refresh of the subscribed threads view won't solve it immediately. Even if my next unread post is, say, the 3rd on the next page, I'll still be taken to the top of the previous page and therefore not land on the right post (correct anchor, but wrong page). Something to do with caching, perhaps?
Click to expand...
Click to collapse
+1
I have recognized this radom issue from time to time in xda app and on my PC.
The last few times when the jump to first unread post failed (jumped to the wrong post), there was a new page in the thread.
And instead of jumping to the first post on the last page of the thread, this action jumped to the first post on the second-last page of the thread (which was the last page before the new post was added).
But I also recognized the issue, that the jump to first unread post lead me to the last post of the thread, even if I have not read one or two posts before this last post.
The strange thing is that this function works correct most of the time ... only sometimes it misbehaves.
Same problem here! Will anyone fix this?
BUMP! When will this be fixed?
kevindd992002 said:
BUMP! When will this be fixed?
Click to expand...
Click to collapse
Bump again, still not fixed and very annoying.
I'm having issues recreating this problem. We have a query that is similar to the one you said but a little bit different, also there are also factors that may be playing into consideration such as if a post was deleted and I'm wondering if that might be returning the incorrect offset. Can you give me steps to reproduce this again? Is it only threads where you have an unread post count = the number of posts per page?
bitpushr said:
Can you give me steps to reproduce this again? Is it only threads where you have an unread post count = the number of posts per page?
Click to expand...
Click to collapse
For me, using the 2010 interface, anytime on any thread, when I use the shortcut sent to me via an email sent by the XDA website, or use the jump to first unread button it will normally go to the top of the page of the last page I read. Then the next several times I use a shortcut to the thread it goes to that place even when more pages are used and I've read through them all. Then after several visits it will reset and go to the top of the last page I visited again.
I use 50 posts per page. And using the 2010 interface, it NEVER goes to the first unread post whether I use a shortcut from an email sent by XDA or using the button on the top of the page.
Thanks for the help.
Lately I haven't come across this issue, or at least I haven't noticed. I'm not sure if it's because the frequency I check the forum is quite lower, if something was fixed / updated on the server, if it's because I'm now using the 2013 Beta theme instead of the 2013 Beta - 1024 I used before, or something else.
I'll keep an eye out, though, and post here if I do come across this problem again with as much info I can infer from the situation.
Tungstwenty said:
Hi,
I use a lot the small arrow to the left of each subscribed thread to jump to the 1st unread post.
Most of the time it works correctly, but from time to time it will show me the start of the previous page and be left at the top, since the URL anchor is not present on that page.
The original link will be something like ".../showthread.php?goto=newpost&t=nnnnnn", which later resolves to ".../showthread.php?p=mmmmmm#postmmmmmm".
The problem is that "showthread.php", when processing with the "p=..." argument, sometimes fails and presents the previous page than it should. If I were to replace "p=mmmm" by "t=nnnn&page=yyy", leaving the anchor, it will work.
Based on some experiments, my guess is that that php, when processing in the p= mode, fails to handle the edge case where post_count mod page_length is 0. I tried it with multiple page sizes, and for the case I was trying it (before I read the post and now need to wait for another case like this), the post was a multiple of 10, 20, 30 and 40 but not 50. So, only after changing the page length to all values to confirm it was failing, and finally to 50, did it work properly.
I normally use 20 posts per page so the chances of the last unread being a multiple of that are pretty slim, but those using 10/page are likely to experience this more often.
FIX: The formula for the page count "page_number=((post_count - 1) DIV page_length) + 1" or equivalent. Currently there's an offset of 1 that probably nobody ever complained about (at least I didn't find any post mentioning this).
This occurs regardless of the selected theme, and also on the XDA app (the server side is probably the same, or shares that part of the code).
EDIT: It appears that the conditions are not that simple. Sometimes, *after* the situation has been triggered (or so it seems), refresh of the subscribed threads view won't solve it immediately. Even if my next unread post is, say, the 3rd on the next page, I'll still be taken to the top of the previous page and therefore not land on the right post (correct anchor, but wrong page). Something to do with caching, perhaps?
Click to expand...
Click to collapse
BUMP! When will this be fixed?
Hi - My internet browser is Firefox, and I have been using NoScript for years.
There is only one website that causes me constant problems when browsing: XDA Developers.
I use NoScript constantly with a lot of stuff disabled by default: Everything Facebook is always disabled, along with doubleclick and a bunch of other tracking websites.
With NoScript on, the XDA screen is constantly jumping around, with various websites constantly trying to refresh about twice a second. It is so jumpy with embedded websites continuously refreshing, that I can't even control NoScript well enough to enable whatever disabled website(s) are causing the problem.
I wouldn't be frustrated if this happened to me all the time, but XDA is the only website I see this problem on. I would expect a high-tech developer website like XDA to have less problems instead of more problems.
Sigh. I wish somebody at XDA could fix this.
¿GJ?
NoScript has a whitelist feature. If you don't want to use it, you can't expect it to be "fixed" (actually, modified to fit your needs would be a better choice of words) anytime soon, as the forums (and many other forums, in general) rely rather heavily on scripts.
I personally have XDA added to my whitelist.
As for the refreshes, did you make sure it's not another add-on that's conflicting? Start FF in safe mode and check if the issue persists.
Don't know if this helps, but I just tested XDA with NoScript without any issues.
That being said, a lot of features rely on JavaScript, so no guarantee what would happen if you only turned on some of them.
Huh.. I use NS on FF, and have seen no issues. To be sure it is NS, have you told it to temporarily allow all, and see if that fixes it? It could certainly be another issue..
What he could be speaking of is the portal constant refreshing (not on the forum), which also occurs on my differents computers with NS (with xda on whitelist).
For me, everytime I scroll on the portal main page, it refresh itself.
It's weird - Something changed between yesterday and today. Yesterday, this page wouldn't sit still until I was able to do enough "Temporarily allow all this page" button presses (about 5 or 6) to get the page finally stabilized.
Now, everything was stable when I entered XDA with the same "allow" list I had yesterday.
I'm not a big fan of "White List"ing sites, since so many sites have Facebook embedded in them (amongst many other tracking sites I don't like). Ever since Facebook violated my privacy and sucked up my personal contact information without my explicit approval, I ... ...
... well, let's just say I won't "Like" Facebook.
I appreciate the feedback from y'all, and I wish I knew what changed.
Thanks!
¿GJ?
bitpushr said:
Don't know if this helps, but I just tested XDA with NoScript without any issues.
That being said, a lot of features rely on JavaScript, so no guarantee what would happen if you only turned on some of them.
Click to expand...
Click to collapse
Divine_Madcat said:
Huh.. I use NS on FF, and have seen no issues. To be sure it is NS, have you told it to temporarily allow all, and see if that fixes it? It could certainly be another issue..
Click to expand...
Click to collapse
Some forum features won't work: dropdown menus (e.g. "Go to Page" next to the page numbers, "Quick Links", "Rate thread") search boxes not being cleared automatically when you click them, username/device completion in search boxes or using the new mention feature, share buttons (they won't show how many times X got shared), etc. The WIYIWYG editor obviously doesn't work as well.
The portal's layout is a bit messed up, too.
It's all fixed by adding xda-developers.com to the whitelist. I think you both already have it added (I removed it for testing), which is what you're supposed to do for websites you trust anyway.
---------- Post added at 12:01 PM ---------- Previous post was at 11:53 AM ----------
¿GotJazz? said:
It's weird - Something changed between yesterday and today. Yesterday, this page wouldn't sit still until I was able to do enough "Temporarily allow all this page" button presses (about 5 or 6) to get the page finally stabilized.
Now, everything was stable when I entered XDA with the same "allow" list I had yesterday.
I'm not a big fan of "White List"ing sites, since so many sites have Facebook embedded in them (amongst many other tracking sites I don't like). Ever since Facebook violated my privacy and sucked up my personal contact information without my explicit approval, I ... ...
... well, let's just say I won't "Like" Facebook.
I appreciate the feedback from y'all, and I wish I knew what changed.
Thanks!
¿GJ?
Click to expand...
Click to collapse
I would suggest using something that will block them on all websites, then. You can probably do it using NoScript's advanced filtering options, but I personally already use AdBlock Plus, and there's a neat list you can subscribe to that will block all those buttons. Get the "Annoyance Block List" from here.
¿GotJazz? said:
It's weird - Something changed between yesterday and today. Yesterday, this page wouldn't sit still until I was able to do enough "Temporarily allow all this page" button presses (about 5 or 6) to get the page finally stabilized.
Now, everything was stable when I entered XDA with the same "allow" list I had yesterday.
I'm not a big fan of "White List"ing sites, since so many sites have Facebook embedded in them (amongst many other tracking sites I don't like). Ever since Facebook violated my privacy and sucked up my personal contact information without my explicit approval, I ... ...
... well, let's just say I won't "Like" Facebook.
I appreciate the feedback from y'all, and I wish I knew what changed.
Thanks!
¿GJ?
Click to expand...
Click to collapse
I have the opposite problem it seems, in that if I white-list the site then quite often one of the scripts goes haywire
and refreshes the page repeatedly for several refreshes or until the server complains with an error message about being overloaded.
It has been suggested to me that this may be a 2013 theme problem, so I'm trying the 2010 one for a few days to see if that fixes it.
Nameless One said:
I have the opposite problem it seems, in that if I white-list the site then quite often one of the scripts goes haywire
and refreshes the page repeatedly for several refreshes or until the server complains with an error message about being overloaded.
It has been suggested to me that this may be a 2013 theme problem, so I'm trying the 2010 one for a few days to see if that fixes it.
Click to expand...
Click to collapse
@Nameless One: Yes, I've been seeing the "Server Overloaded" error message as well. I wasn't sure if it was NoScript related, though I was beginning to suspect it. I would open the same XDA pages in IE or Chrome without any problem, but see the "Overloaded" error only with Firefox. Usually (but, not always), temporarily enabling all sites fixed that problem for me.
¿GJ?
I have the same constant refresh problem.
The site only works if I set noscript to allow everything globally or if I use IE (ouch).
It feels to me this site is overburdened with ad/tracking scripts and blocking them forces the site to break (admins anti block?).
I will try the 2010 theme idea and report back, also I do have the main domain whitelisted.
--edit--
2010 theme fixes it, so I guess a 2013 theme issue.
Yep - Dumped the 2013 Theme and went back to 2010 Theme.
Everything's groovy now.
¿GJ?
¿GotJazz? said:
Yep - Dumped the 2013 Theme and went back to 2010 Theme.
Everything's groovy now.
¿GJ?
Click to expand...
Click to collapse
2013 relies heavily on javascript so I imagine that is why you are having some issues. 2010 uses it much less but you may still see some issues relating to Javascript being blocked, such as menus not working and that sort of thing.
browser: firefox 24
system: ginux (debian wheezy)
problem: when using the no-script or script-block addons it results in XDA pages refreshing repeatedly, and, double posts, etc. the only pages that are not affected are "thread views" and "new reply". xda has been allowed to run scripts, but not google, etc. suspect that xda's scripts are checking to see if their advertizers script's loaded, and, if not, refresh the page. would not mind allow ads for xda, but, it would mean allowing that ad-site globally or permanently, which i don't want. will try to find a setting that lets me allow them only for xda...
I'm using Chrome and getting the same thing. I also use Ad-Block. Not sure what is causing it but I haven't tried disabling the Ad-Block (which I won't disable just to view XDA).
It just seem to start a few days ago. I've posted this behavior else where and edited my post with a link here to help keep it all together. I'll disable Adblock when I reply to this and edit with my findings.
Edit:
Disabling AdBlock does NOT fix the problem for me on Chrome. When it turned off, I was still greeted with a double post error message.
We have seen reports of this here but I haven't been able to narrow it down. I suspect it has something to do with selective script blocking in some addons. Please use the 2013-1024 theme which disabled the sidebar and should clear up the reloading issue for you.
Closing this thread since this is already being discussed over there.