Long links still broken within a post - HotUKDeals
We use cookie files to improve site functionality and personalisation. By continuing to use HUKD, you accept our cookie and privacy policy.
Get the HUKD app free at Google Play

Search Error

An error occurred when searching, please try again!

Login / Sign UpSubmit

All Comments

(26) Jump to unreadPost a comment
Comments/page:
#2
Sorry we will take a look at this, its not really long links that are the problem, its the characters that are in the links, the longer the link is the more likely it is to have some characters in there that aren't really supposed to be in a link.
#3
Whilst you're working on the automatic parsing of hyperlinks, do you think you could consider adding the same functionality in "Private Message" text?

At present (& since the site redesign of last year), any hyperlinks in the text are left so that they cannot be clicked (as is the case with comments in threads).

Thanks for your consideration. I have mentioned this before in one of the original combined bug/issue threads.

(Sorry csiman).

BFN,

fp.
#4
fanpages
Whilst you're working on the automatic parsing of hyperlinks, do you think you could consider adding the same functionality in "Private Message" text?

At present (& since the site redesign of last year), any hyperlinks in the text are left so that they cannot be clicked (as is the case with comments in threads).

Thanks for your consideration. I have mentioned this before in one of the original combined bug/issue threads.

(Sorry csiman).

BFN,

fp.


Ive added that into the feature request list, I am not sure how soon we can get that in there but its on the list.
#5
Developer
Ive added that into the feature request list, I am not sure how soon we can get that in there but its on the list.

Thanks.

I appreciate it isn't a major issue but it was a feature that was removed with the new site roll-out.

Whilst we're on the, erm, subject "Re:" is still being prefixed on "Private Message" replies, so that after a few replies between parties the subject reads "Re: Re: Re: Re: (original subject)".

(The number of messages is not updated after deleting. The upper limit of 100 is not adhered to. You cannot add a member as a Blind Closed Copy recipient. You cannot send messages to more than one member concurrently. All features removed; so arguably should not be in the "feature request" list. The Bcc & concurrent recipients features are particular useful when sending messages to somebody & copying Admin or any of the other site representatives).


Is there any chance of seeing what is within the "feature request" list &/or the "bug/issue" list?

BFN,

fp.
#6
Just for clarity...
Developer
Ive added that into the feature request list, I am not sure how soon we can get that in there but its on the list.

Do you mean it wasn't in your list(s) before I mentioned it above (today)?

Would you like me to re-list all the outstanding issues (many) other members & I logged in the dedicated threads in July, August, & September last year so you can make a note of them, or did I misunderstand your response about adding something to a list that has already been reported (twice, by me)?

BFN,

fp.
banned 1 Like #7
Developer
Sorry we will take a look at this, its not really long links that are the problem, its the characters that are in the links, the longer the link is the more likely it is to have some characters in there that aren't really supposed to be in a link.

you put the characters in the link! oO

It is an ADVANCED SEARCH result URL X)


Edited By: csiman on Mar 10, 2011 16:21
#8
csiman

you put the characters in the link! oO

It is an ADVANCED SEARCH result URL X)

Yeah, the characters get automatically URL encoded by the browser though, whats tricky about that is knowing when the link stops and the comment re starts when there are non url encoded characters in the link.
#9
Developer
csiman
you put the characters in the link! oO It is an ADVANCED SEARCH result URL X)
Yeah, the characters get automatically URL encoded by the browser though, whats tricky about that is knowing when the link stops and the comment re starts when there are non url encoded characters in the link.

If you are encoding non-displayable ASCII characters & space characters in the Uniform Resource Locator address then the link stops at the first space character or any non-displayable code (Carriage Return, Tab, Line Feed, & so on) or when the last character in the comment is reached.

If anybody pastes a link & it runs into some other text (without a space character in between) then they need educating.

BFN,

fp.
#10
fanpages
Just for clarity...

Do you mean it wasn't in your list(s) before I mentioned it above (today)?

Would you like me to re-list all the outstanding issues (many) other members & I logged in the dedicated threads in July, August, & September last year so you can make a note of them, or did I misunderstand your response about adding something to a list that has already been reported (twice, by me)?

BFN,

fp.

There is a distinction between bugs and requests. Bugs are automatically put on the list of things to fix, and prioritized based on different factors, but we try and fix them asap (we have been increasing the amount of time we put on fixing lingering bugs recently). Requests are not automatically put on a list of things to do, if several people are asking for the same thing we definitely look hard at what it would take to put in, and if it makes sense overall. Requests do not however automatically get done because someone brings it up.

I think more visibility on what requests users currently have and maybe even a voting scheme for them, so we can better prioritize what the community wants might be in order here.
#11
Developer
fanpages
Just for clarity...

Do you mean it wasn't in your list(s) before I mentioned it above (today)?

Would you like me to re-list all the outstanding issues (many) other members & I logged in the dedicated threads in July, August, & September last year so you can make a note of them, or did I misunderstand your response about adding something to a list that has already been reported (twice, by me)?


There is a distinction between bugs and requests. Bugs are automatically put on the list of things to fix, and prioritized based on different factors, but we try and fix them asap (we have been increasing the amount of time we put on fixing lingering bugs recently). Requests are not automatically put on a list of things to do, if several people are asking for the same thing we definitely look hard at what it would take to put in, and if it makes sense overall. Requests do not however automatically get done because someone brings it up.

I think more visibility on what requests users currently have and maybe even a voting scheme for them, so we can better prioritize what the community wants might be in order here.


Firstly, thank you for looking at the issue with replying to text & the line feed/carriage returns being removed. I see there is now an additional set of [CR][LF] characters at the start of this reply but that is a small price to pay for the number of months the issue has been present. I am currently using Mozilla Firefox 3.6.15. I will reply to a thread in office hours tomorrow (where I am restricted to) using Microsoft Internet Explorer 7.x to see if the issue is no longer present in that web browser (too).

Yes, I appreciate there is a difference between a bug & a feature request (as I do have a background in hardware & software testing), but thank you for clarifying the approach you adopt addressing reported issues.

However, when features have been removed then it is not a request (to reinstate them); their absence is missing functionality from the previous iteration of the site & these should be seen as a "bug" because the features/functions no longer work (or work differently).

I do not know if you were originally involved with the site redesign, or when you joined the team, but the main crux of the disgruntled nature of the (long-standing) users of this site is...

a) A Beta version of the site was offered for preview. Faults were recorded & sent to the site representatives. It appeared nothing was acted upon before the site was deployed (live) just a few hours later.

b) Many members lodged their complaints & issues with the new site in the first day of release. The same members continued logging issues for several weeks hoping for feedback on those they had previously logged Only the most critical issues were addressed (as you would expect), but some of the faults recorded during the initial days are still present today.

c) Logging of faults/issues/bugs/queries & so on has taken a few forms, but it seems that all the effort everybody undertook for the first couple of months has been brushed under the virtual carpet as when the same issues are re-logged now you (& your colleagues) seem to react like it is the first time anybody has mentioned them. Just note how many times I mention (as logged previously) in Feedback threads!

d) Faults are introduced when new functionality is made available. Many of these are seemingly present because testing is not performed across all the most popular web browsers (as summarised by you earlier today; but this summary was also provided by Admin a few weeks ago, and) we are still finding that some functions work in Mozilla Firefox but are less than satisfactory in Microsoft Internet Explorer.

Frankly, do you not test across a range of web browsers before realising code to the live environment? If you do not, this would explain the issues we see. If you do, then your testing approach needs revising because you are missing problems that can be reproduced very easily.

e) We receive replies like "We'll look into that" & that is the last we hear until we raise the issue again weeks later. It seems that replies of that nature should actually be read as "We'll log that in our list but not look at it yet".

f) New functionality is being introduced (like the "badges", & the "Saved Deals") when long-standing faults remain. I hope you can see how this just annoys those with genuine reasons for complaint.


Others may well have other points to add, & I have endeavoured to keep this list to a minimum to make the points made clear. I could go on, & may well do if you ask me to! :)

I personally have tried to help resolve the issues in the past. I offered my help & engaged in discussions (privately) with two site representatives & they welcomed my input. I did have better (read: more important) things to do personally, but I was willing to put these to one side to help the community here.

However, certain members tried to derail my efforts & when I didn't receive the support of the site representatives (one of whom seemed to be sharing a joke at my expense in one case) I took that to mean my efforts were being overlooked so I did not proceed any further.

The initial set of threads to record issues were then closed (& taken offline!) & the logging started again. Some of the same issues were recorded & we initially had daily updates on progress. This then changed to updates every few days, then once a week, then no updates on progress at all.

That thread was then closed & we were asked to log all new issues in separate threads indicating our own classification of the point being raised (bug, feature request, query, & so on).

Months have now passed & the Feedback forum is full of unresolved issues. Some are repeated because there does not seem to be any control/collation, some ask for more information that is provided but then the dialogue stops (until the next time the issue occurs), other threads turn into complaints about the site & the situation we are in today, other people just cannot be bothered to offer feedback any longer; some established members have stopped contributing to the site at all (& their absence, in my opinion, is a loss to the community as a whole).

I trust you do not feel that I am criticising you personally. I have tried to be restrained with my responses in the past to not be overly-negative, but I am beginning to think that the only way to highlight the poor state of management of the site recently is to be honest.

BFN,

fp.
#12
Thanks for that reply, I will try and shed a little bit of light on how we have been trying to handle things. First, you could say I was the first one on the team in a manner of speaking, so yes I am aware of what happened during the rollout, we call that rollout the dark days, and it was pretty bleak for a while. I don't want to revisit that topic though as I don't think it would be constructive, there were a lot of hard lessons learned from that release from the people on the team.

[quote]b) Many members lodged their complaints & issues with the new site in the first day of release. The same members continued logging issues for several weeks hoping for feedback on those they had previously logged Only the most critical issues were addressed (as you would expect), but some of the faults recorded during the initial days are still present today.


The first couple months after the release was nothing but bug fixes, and I would estimate we fixed hundreds of bugs, and we were definitely listening to what users were posting, even if we didn't always have the time to post a response that we had fixed something they brought up.

c) Logging of faults/issues/bugs/queries & so on has taken a few forms, but it seems that all the effort everybody undertook for the first couple of months has been brushed under the virtual carpet as when the same issues are re-logged now you (& your colleagues) seem to react like it is the first time anybody has mentioned them. Just note how many times I mention (as logged previously) in Feedback threads!


Of the bugs that I see left here, they seem to be the low priority ones that have been being trumped by other things, or things that are difficult to replicate, which unfortunately bump them down the list sometimes. We are refocusing our efforts recently on clearing these bugs, which is why you might notice things from quite a while ago are being fixed up. It is really useful when people bring things up a second time, as it brings things to our attention quite a bit faster.

d) Faults are introduced when new functionality is made available. Many of these are seemingly present because testing is not performed across all the most popular web browsers (as summarised by you earlier today; but this summary was also provided by Admin a few weeks ago, and) we are still finding that some functions work in Mozilla Firefox but are less than satisfactory in Microsoft Internet Explorer.


Bugs are a fact of software development. What I consider often times is what is our bug rate like compared to similar sites. I am really not sure on that one. I once compared the number of bugs we get vs the number of bugs vbulletin has reported, and we were definitely not the losers there. We are experimenting with new ways of improving our quality though, every developer would like to put things out that are totally bug free. As far as cross browser testing goes, we played around with a lower level of support for IE6 (especially when we launched the last update) but there are still a lot of people in the community who use those browsers so we definitely do test all our functionality in all browsers. Our cross browser compatibility has definitely suffered since the last update, but its something that we we working on improving.

e) We receive replies like "We'll look into that" & that is the last we hear until we raise the issue again weeks later. It seems that replies of that nature should actually be read as "We'll log that in our list but not look at it yet".


Some bugs we fix right away and others do go on a list and wait, a lot of it really depends on how much work there is to do and how much time we can put into fixing bugs. We are certainly dedicating more time to bug fixing now though to try and clear up the lingering issues.

f) New functionality is being introduced (like the "badges", & the "Saved Deals") when long-standing faults remain. I hope you can see how this just annoys those with genuine reasons for complaint.


The badge changes were in response to quite a few complaints about the badges, so we're caught there, there are a lot of members in the community who want a lot of different things, even there were a lot more of us we could give everything to everyone at the same time, but unfortunately there are only a couple of us so we have to do things one at a time.
1 Like #13
Thank you for your reply.

Developer
The first couple months after the release was nothing but bug fixes, and I would estimate we fixed hundreds of bugs, and we were definitely listening to what users were posting, even if we didn't always have the time to post a response that we had fixed something they brought up


"hundreds"? Does that not strike you as too many for a site of this size/complexity?
As I mentioned above, the site was released without acting upon issues raised during the few days of "Beta" availability.

Was inadequate testing the cause of this many faults?

Developer
Of the bugs that I see left here, they seem to be the low priority ones that have been being trumped by other things, or things that are difficult to replicate, which unfortunately bump them down the list sometimes. We are refocusing our efforts recently on clearing these bugs, which is why you might notice things from quite a while ago are being fixed up. It is really useful when people bring things up a second time, as it brings things to our attention quite a bit faster.


New functionality is still being introduced (some of it with faults as well) though.
How can you justify adding new features when the existing ones do not function correctly?

Developer
Bugs are a fact of software development. What I consider often times is what is our bug rate like compared to similar sites. I am really not sure on that one. I once compared the number of bugs we get vs the number of bugs vbulletin has reported, and we were definitely not the losers there. We are experimenting with new ways of improving our quality though, every developer would like to put things out that are totally bug free. As far as cross browser testing goes, we played around with a lower level of support for IE6 (especially when we launched the last update) but there are still a lot of people in the community who use those browsers so we definitely do test all our functionality in all browsers. Our cross browser compatibility has definitely suffered since the last update, but its something that we we working on improving.


I don't wish to tell you how to do your job, but I do have (a lot of) experience in software development.

Yes, bugs are to be expected. With adequate testing these are minimized or eradicated. One can only imagine how many faults were in the code prior to testing if there are so many present after it!

Taking your example of vBulletin; that has much more (flexible) functionality than the fixed/bespoke implementation of the HotUKDeals site. It is to be expected that more issues are recorded in a system that allows configuration by the user base as not every combination of operating system/web browser & individual client configuration can reasonably be expected to be tested on each & every release.

That is not the point though; you are not any other site. You should be striving to have no faults, not less than anybody else!

Re: IE6 - I thought you were suggesting that IE6 is not a widely-used browser yesterday (with 7.49% of the 38.33% of total Internet Explorer users of the site). Why the emphasis on this specifically? It was introduced in 2001 & superseded by IE7 in 2005. 7.49% of 38.33% is around 2.8% of total users of the site. If those percentages do not take into account unique users then that figure is smaller again.

I accept that everybody should have access regardless of the age of their web browser (within reason) but why the need to concentrate your efforts now? Wasn't this browser taken into account previously? If not, why not?

Developer
Some bugs we fix right away and others do go on a list and wait, a lot of it really depends on how much work there is to do and how much time we can put into fixing bugs. We are certainly dedicating more time to bug fixing now though to try and clear up the lingering issues.


As I mentioned yesterday, having sight of these lists may help us to help you. We may be able to remove items that have been fixed but you have not re-tested, or we may be able to re-prioritise or move items from one list to another.

Developer
The badge changes were in response to quite a few complaints about the badges, so we're caught there, there are a lot of members in the community who want a lot of different things, even there were a lot more of us we could give everything to everyone at the same time, but unfortunately there are only a couple of us so we have to do things one at a time.


The fact you introduced the badges at all (prior to amending them & finding the changes did not function as intended) when outstanding issues remained was the point I was trying to make.

How many people do you think wanted the badges? I do not recall being asked.


I do appreciate you have limited resources to resolve issues, but a lot of work went into compiling the initial bug threads & testing/re-testing issues. I installed four browsers on my own PC to aid diagnostics/analysis of other user's issues & regularly reported when something was reproducible or not.

In one of your responses above you said that "things [that] are difficult to replicate". If you are having trouble reproducing issues all you need to do is ask for others to try the same feature or function that has led to a Feedback thread being created.

Some of us want(ed) to help (initially).

If you alienate enough people with little or no communication, you risk loosing what little help there is left (if you feel you need it).

Again, hoping not to sound confrontational; simply stating facts as I see them.

BFN,

fp.

PS. Further comment: [ http://www.hotukdeals.com/feedback/how-can-unsubscribe/978531?p=11750372 ]

Edited By: fanpages on Jul 17, 2011 09:04: Added link to recent comment in another thread
#15
short links are broken mostly ending in
<br /


as you cannot post it or you will see nothing) after posting correct link)


after posting a correct link






Edited By: dontasciime on Sep 22, 2011 17:08
#16
lol site is cabbaged
1 Like #17
dontasciime
lol site is cabbaged


Lettuce know what you really mean.
#18
fanpages
dontasciime
lol site is cabbaged

Lettuce know what you really mean.


Listen marrow enuff of the veggie jokes. I've bean trying to say after posting links they appear with those br HTML and when editing the post everything I type vanishes/lol
1 Like #20
Fix should be out in a matter of minutes.
#21
HeroDeveloper
Fix should be out in a matter of minutes.

mange tout
#22
HeroDeveloper
Fix should be out in a matter of minutes.




The leek appears to have been fixed, Hero'.

Thanks.
#23
Related issue?

Quoting Comment #3 in this thread...

[ http://www.hotukdeals.com/deals/borderlands-game-year-edition-was-27-99-now-11-99-european-playstation-store-1025973?p=12366324 ]

Presents this (as seen in Comment #4)...

sits69
Great price for the PSN copy -- also available as a physical disc for about the same price from The Hut:

[url=http%253A%252F%252Fwww.thehut.com%252Fgames%252Fplatforms%252Fps3%252Fborderlands-game-of-the-year-edition%252F10240126.html]http://www.thehut.com/games/platforms/ps3/borderlands-game-of-the-year-edition/10240126.html[/url]

with the 10WED discount (or other similar TheHut discounts). Might be useful for some of you out there who are starting to run low on PS3 HDD space (like me!)....


BFN,

fp.
1 Like #24
This is actively being worked on.
1 Like #25
The issue in your last post, FP, should be fixed. However the existing ugly link won't be over-written. If you'd like, I can edit your comment for you to fix the link. Rest Easy, Citizens.
#26
HeroDeveloper
The issue in your last post, FP, should be fixed. However the existing ugly link won't be over-written. If you'd like, I can edit your comment for you to fix the link. Rest Easy, Citizens.


No need, Hero', thank you.

Thanks for you prompt attention to this too :)

Post a Comment

You don't need an account to leave a comment. Just enter your email address. We'll keep it private.

...OR log in with your social account

...OR comment using your social account

Thanks for your comment! Keep it up!
We just need to have a quick look and it will be live soon.
The community is happy to hear your opinion! Keep contributing!