Agreed not fixed - just went to check and in the middle of trying to get the actual, real list of new releases it came up with someone elses name.
Slight addendum - the displaying of errant names may have been fixed (maybe by a change of the html/php to just output the literals ‘Log out’ or ‘Login’) but I still get ‘random’ numbers for items in wishlist and the recent release list is still a complete lottery
All others from pulldown menus seem to work OK. I’ll poke at couple of things, but I confess I was kind of too hopeful myself that this particular gnat of a bug had been squashed… ah well, crow is tasty and at least I’m not the one who needs to fix it. :/
We are aware that many of you have seen in the DAZ Store another name than yours. If you happen to continue to see on our store, If you are not “Some Other Name”... The solution is to Clear your Cache and Cookies in your internet browser, then force a refresh on the page. The problem will now be taken care of and you should never see this again.
This is unfortunately not correct; YOUR cache (i.e. DAZ’s) is still broken. The wishlist count on /shop and /shop/shop continue to be wrong, as indicated by another user, and while you’ve hidden the user’s names, the wishlist count is obviously an indication that it’s rendering the wrong user’s information there.
DAZ_bfurner - 06 June 2012 12:10 PM
As a reminder: This has never given you access to others account data. Your account is and has always been safe.
Thankfully, outside of real names, this is definitely true. When the site actually has to resolve who you are, it’s getting it right, but when it’s showing you some stuff (presumably varnish cached for performance) like user’s name, wishlist count, and required products, it’s just plain wrong as often as it’s right. :( I’m all good for slack in fixing this, go for it, take your time and do it right, but don’t assert that’s the problem when it’s not. It may have been _one_ of the problems, but it is not this problem. If it were, I would expect that users would have been consistently seeing the same user’s name in that location.
Best of luck fixing this, hopefully you’re continuing to try, not thinking that this’s resolved it…
Edited to attach screencaps of what I mean. I have none of those items in my wishlist, and I have half that number of wishlist items.
Other places are showing no names right now, so echoing what Morgan is saying, looks like they are hidden. I get different wrong wish lists at:
...i was going to list several addresses that were wrong and several that had been showing me correct wish list info, but some of those just switched to somebody else, so never mind, it still appears inconsistent.
Just to keep up the drumbeat, underlying cache problem definitely not fixed. Good luck, hope you guys get to the bottom of it.
Also, I have seen a name/wishlist instance that I recognized as someone on the forums on one occasion.
I already did this as soon as the new store first showed up, and I do a force-refresh several dozen times per session in a mostly vain attempt to view a current store page with all new stuff on it. I still regularly see the “not someone else” link. Do I need to clear cache and cookies again?
I would do that.
OK, I just did it. At first it didn’t work, I was still seeing the total for someone else’s wishlist — although always the same one this time, with 305 items. After bouncing around the store for a few minutes, it seemed to “take” — new things show up on the “New Releases” page, the order doesn’t change when I refresh again, and I had the right number of things in my wishlist.
Unless I’m on the site homepage, which has a 58-item wishlist (wrong) and the store homepage, which doesn’t show a wishlist total.
Still a bit broken, but sorta useable. Next, I’ll watch the prices and see if they’re bouncing/going on and off sale over the next couple of days. There’s stuff I want to buy, but right now I don’t trust the store prices.
I just realized that many ISPs cache sites. Even in the company I work at, when I change web content, I start getting erratic results and I begin frantic debugging. Now I realized the site cacheing ‘feature’ so I now take a break for an hour or so to let the cache flush.
Also working with other sites ‘change’ exposed problems with hosting companies using cloud distributed load balancing ect…
I had to wait 24 hours for changes to take effect and verified. If the change was wrong, then another 24 for the undo and then submit the next try.
So much code seens to only work on the server published too and if the cloud is large (many servers around the world) any changes may not work because it conflicts with other servers current data. Bring down a web server, upload the new page, start the server. How long will it take to cover all the servers that most Site Hosts don’t even know exits.
I think DAZ might have not only changed the application foundation but also the Site Host.
One of the departments at my work published a web app and I had to install firefox on all computers because the app was developed on a MAC and does not work right with IE. It has always been a big issue testing a web site on all browsers across all devices.
Everyone clearing their cache has little effect. Its the ISPs that need to do this.
Ok, I have no idea if this will be helpful to anyone, but this pattern is consistent between my computer and another device I have, after having cleared both at fairly spaced apart times today.
Green boxes mean that page shows my correct wishlist count. Generally subcategories beneath show correct as well.
Blue boxes mean it does not reveal any information, name or wishlist.
Red boxes mean it shows wrong count in the wishlist.
Double red (only DAZ3D main home page right now) shows wrong wishlist and wrong name.
also that green box next to the blue box at DAZ Studio products link indicates its subcategories all were green. I should have probably put a green box next to the red one for People, since it looked like most subcategories would have been green, but I didn’t check them all. This may be futile, but if it’s true for others as well, it may help in some way, or if it’s not the same, it means the behavior is still not consistent, EDIT or the problem is happening at another link in the chain as bbroussard says above.