Replicating this problem is inconsistent at best for myself; however, when it does happen, the build finder still seems to work in finding the builds you're looking for---it just also produces an annoying error.
Replicating this problem is inconsistent at best for myself; however, when it does happen, the build finder still seems to work in finding the builds you're looking for---it just also produces an annoying error.
It would be REALLY NICE if we could enter spells like "Skeletal Mage" again.
If you press the "Filter" button without enrtering items or non-items, the scripts generate this URL:
I'm having the same issue, and I've tried on various browsers and machines. Keep getting "Error" Sorry an error has occurred. Does the administration of this website not care? Its been like this for weeks.
The issue causing errors when visiting build pages has proven tough to track down, and the dev team had been implementing temporary fixes until the root cause could be determined. A more permanent solution has been deployed, and you should experience less errors when visiting builds!
The problem isn't when visiting build pages though, it's when trying to filter for particular builds. You are correct that the "undefined is not a valid number." error that appears next to the Has Item/Doesn't Have Item boxes does not actually affect the results of filtering. Regardless of if they are left empty or not the other filtering options do work. EXCEPT for the Has Spell filter option.
Typing anything into that field does not give a list to select from the way the Item boxes do and even if you type in the exact spell name the filter doesn't actually use that criteria. For instance, if I type in Disintegrate for Has Spell and hit filter the results I get are no different than if I leave that filed blank and hit filter. Essentially it appears that the Has Spell option is completely broken currently.
Just to add some additional info, I have tried filtering for build numerous times over the last 24 hours including just before posting this and have seen no change in the issues occurring. Again, tested with Firefox, Internet Explorer, Chrome & Edge and with a number of different ways of filtering.
Any updates on this? The issue is still occuring as of this post, tested on 3 different machines in two different locations and all 4 mentioned browsers on all machines. This really makes finding builds based on a certain spell a huge pain.
Edit: I suppose I should include that all browsers are fully up-to-date as well.
Just a "were aware of the issues but don't have a fix" or "we're currently looking into it" or even just "we don't care, stop asking" would be nice. I mean, we're well into S15 now and several weeks since a dev responded to this thread as well as and still unable to filter builds by Has Spell and still getting the admittedly mostly harmless but annoying undefined messages when not selecting gear when filtering. Would be nice to get any kind of response at this point.
Just a "were aware of the issues but don't have a fix" or "we're currently looking into it" or even just "we don't care, stop asking" would be nice. I mean, we're well into S15 now and several weeks since a dev responded to this thread as well as and still unable to filter builds by Has Spell and still getting the admittedly mostly harmless but annoying undefined messages when not selecting gear when filtering. Would be nice to get any kind of response at this point.
Sorry for the silence, we are working on a solution. No ETA
Sorry for the silence, we are working on a solution. No ETA
Thank you for the response and sorry I came off quite pissy in my post. It felt like this was being ignored a bit so it is nice to get a response that you guys are working on it even with no ETA. Thanks again for the response and the hard work.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I can't select a spell in "Has Spell". No drowdown menu appears at all.
Tested with Edge (W10 1803 Build 17134.285) and FF 62.0 (both 64bit)
Pls fix this
TiA
Tested with Chrome, too. Same results.
Any answer from the webmaster of diablofans.com would be much appreciated !
Thank you for bringing this up, I will look into it.
Any update on this? Still occurring for me at least, tested with current versions of Firefox, Chrome, IE & Edge. Also tried with ad blocker on or off.
Replicating this problem is inconsistent at best for myself; however, when it does happen, the build finder still seems to work in finding the builds you're looking for---it just also produces an annoying error.
It would be REALLY NICE if we could enter spells like "Skeletal Mage" again.
If you press the "Filter" button without enrtering items or non-items, the scripts generate this URL:
https://www.diablofans.com/builds?filter-has-spell-2=-1&filter-build-tag=3&filter-has-item=undefined&filter-no-item=undefined&filter-class=128
The red error Messages get generated because 2 Params are defined as "=undefined" . If you alter the URL manually by removing "undfined" like this:
https://www.diablofans.com/builds?filter-has-spell-2=-1&filter-build-tag=3&filter-has-item=&filter-no-item=&filter-class=128
the resulting Display is fine.
HtH
Build-finder completely broken AGAIN. Can't access ANY build AGAIN.
Error Message: ERROR Sorry, an error occurred while processing your request.
Please fix your Buld-Finder FINALLY.
I'm having the same issue, and I've tried on various browsers and machines. Keep getting "Error" Sorry an error has occurred. Does the administration of this website not care? Its been like this for weeks.
@Mods
This seems tob e an intermittent Problem.
On some Hours of the day you get a Response (build), on some you don't
The issue causing errors when visiting build pages has proven tough to track down, and the dev team had been implementing temporary fixes until the root cause could be determined. A more permanent solution has been deployed, and you should experience less errors when visiting builds!
The problem isn't when visiting build pages though, it's when trying to filter for particular builds. You are correct that the "undefined is not a valid number." error that appears next to the Has Item/Doesn't Have Item boxes does not actually affect the results of filtering. Regardless of if they are left empty or not the other filtering options do work. EXCEPT for the Has Spell filter option.
Typing anything into that field does not give a list to select from the way the Item boxes do and even if you type in the exact spell name the filter doesn't actually use that criteria. For instance, if I type in Disintegrate for Has Spell and hit filter the results I get are no different than if I leave that filed blank and hit filter. Essentially it appears that the Has Spell option is completely broken currently.
Just to add some additional info, I have tried filtering for build numerous times over the last 24 hours including just before posting this and have seen no change in the issues occurring. Again, tested with Firefox, Internet Explorer, Chrome & Edge and with a number of different ways of filtering.
Any updates on this? The issue is still occuring as of this post, tested on 3 different machines in two different locations and all 4 mentioned browsers on all machines. This really makes finding builds based on a certain spell a huge pain.
Edit: I suppose I should include that all browsers are fully up-to-date as well.
Just a "were aware of the issues but don't have a fix" or "we're currently looking into it" or even just "we don't care, stop asking" would be nice. I mean, we're well into S15 now and several weeks since a dev responded to this thread as well as and still unable to filter builds by Has Spell and still getting the admittedly mostly harmless but annoying undefined messages when not selecting gear when filtering. Would be nice to get any kind of response at this point.
Sorry for the silence, we are working on a solution. No ETA
Twiddling thumbs.
PS: @admin: Inserted Picture not showing up AGAIN !
Pls fix this.
Thank you for the response and sorry I came off quite pissy in my post. It felt like this was being ignored a bit so it is nice to get a response that you guys are working on it even with no ETA. Thanks again for the response and the hard work.