Redisplay Messages: Compact | Brief | All | Full Show Messages: All | Without Replies| Author: | lovaquero  | | Posted: | Sep 24, 2014 14:17 | | Subject: | Re: Option to print part number on orders | | Viewed: | 31 times | | Topic: | Suggestions | |
|
| Doh! Scott beat me to it. That is what I get for not refreshing the page before
posting...
|
| Author: | lovaquero | | Posted: | Sep 24, 2014 14:16 | | Subject: | Re: Option to print part number on orders | | Viewed: | 30 times | | Topic: | Suggestions | |
|
| | Got you covered already: |
|
 |
| Author: | lovaquero | | Posted: | Sep 12, 2014 10:34 | | Subject: | Re: Address Format | | Viewed: | 42 times | | Topic: | Suggestions | |
|
| Some food for thought:
(1) If you live in a country that does not use an address format similar to the
US format, then the US format is odd. So trying to fill out a US-address formatted
form would be somewhat confusing, despite that majority of the world using that
format
(2) Some countries do not have zip codes.
(3) You typically do not have to worry too much as the USPS does not deliver
the package and does not have to interpret the address. That is the job of the
Postal service of the coujtry in question, and I am going to postulate that foreign
post service knows how to read that address...
It really is not that big of a deal as long as you follow the format of the address
provided by the Buyer. As long as you have the country USPS will get the package
to that country. If you follow the format provided by the buyer, there is a
high probability that the post service in that country will know how to interpet
the address.
|
|
| Author: | lovaquero | | Posted: | Aug 21, 2014 15:45 | | Subject: | Re: Store View Tabs Missing [SOLUTION] | | Viewed: | 32 times | | Topic: | Suggestions | |
|
| I tried this one with IE8 (win7 Pro, USB basic mouse), but it doesn't seem
to work. And I attempted the full range of zoom 10%-400% in steps and no luck.
What browser/OS are you using Andy?
|
| Author: | lovaquero | | Posted: | Aug 21, 2014 15:42 | | Subject: | Re: Store View Tabs Missing [SOLUTION] | | Viewed: | 26 times | | Topic: | Suggestions | |
|
| Doh! Right, erm left you are!
I mean, yes - you are correct - I meant 'left-click'
/walks away grumbling about the English language
In Suggestions, par016 writes:
| | Good solution, but I think you mean left click.
-Pete
|
|
|
| Author: | lovaquero | | Posted: | Aug 21, 2014 15:10 | | Subject: | Re: Store View Tabs Missing [SOLUTION] | | Viewed: | 69 times | | Topic: | Suggestions | |
|
| I neglected to mention it before, but there IS a user-side workaround (at least
for IE users) to see the store view tabs. This should work until BL dev team
is able to implement a server-side permenant fix.
1 - Right-click on the store title
2 - Continue to right-click while moving your mouse down, as if you are highlighting
text for a copy/paste operation
3 - You will managage to force the hidden-scrollable table to scroll upward,
revealing the store tabs:
|
|
|
| Author: | lovaquero | | Posted: | Aug 21, 2014 13:33 | | Subject: | Re: Store View Tabs Missing [SOLUTION] | | Viewed: | 49 times | | Topic: | Suggestions | |
|
| Yes - that is the first thing I did (the post above is a copy of that email).
And cs_ryan is on it as well 
In Suggestions, StarBrick writes:
| | Wow, did you post this to the helpdesk too?
|
|
| Author: | lovaquero | | Posted: | Aug 21, 2014 12:17 | | Subject: | Re: Store View Tabs Missing [SOLUTION] | | Viewed: | 61 times | | Topic: | Suggestions | |
|
| A (hopefully) more readable image of the code mentioned above.
Apologies on the typos in the OP - I am used to my customize code editor, and
not so much to document creation. 
|
|
|
| Author: | lovaquero | | Posted: | Aug 21, 2014 12:09 | | Subject: | Store View Tabs Missing [SOLUTION] | | Viewed: | 174 times | | Topic: | Suggestions | | Status: | Discarded | |
|
| (Below is the solution to fix the missing tabs problem that currently exists
on Bricklink. It is a copy of the message I sent to admin. Posting it here for
more visibility. It took me longer to make the images and type the note explaining
the solution than it took to find the problem...)
The root cause is directly related to the addition of the 'link' that
switches the pages from Engling Chinese. It forces the HTML table to take
up more space than is necessary, thus pushing the table the contains the tabs
out of the viewable area. The images show the code - it is a true (and badly
done) hack.
Anyway, enough commenaty, here is the fix:
Bricklink Developers & Admin -
Attached is an image detailing the a solution that will correct the tab rendering
(hidden tabs) problem experienced on certain browsers. The problem is a rendering
difference between browsers related to how they interpret and implement HTML/CSS.
------------------------------------------------
The Root Cause is a combination of the following:
------------------------------------------------
1 - HTML4 v HTML5 support on BL (related to Splash page problems as well)
2 - Old ASP framework code v Modern HTML/CSS standards
3 - A really bad code hack to provide the link to switch to Chinese BL (I mean
no offence - there is no other way to describe it)
4 - Insuffient testing before release.
--------
Code Fix:
--------
#1 - Change the table tag's CELLPADDING attibute from CELLPADDING="5" to
CELLPADDING="0" (It is not needed, but the 10px vertical pixels it frees up are
needed
#2 - ADD "margin:0;padding:0;" to the style attribute of the UL tag utilized
to implement the Chinese language switch (most browsers will automatically do
this, others will not until forced to. This will stop the parent table from
pushing the tabs out of the viewable space in the top frame.
#3 - Add VALIGN="TOP" to the TD tag that wraps the section containing the Store
flags. This will force the flag images to the top of the table, similar to what
is done with the BL logo
Another temp solution is to set SCROLLING="YES" for the FRAME that loads the
store banner and tabs. This would also allow folks to atleast scroll down the
tabs
The Permenant solution is to fix the code hack used to implement the Chinese
language page link. It is improperly implemented - you shouldn't be using
UL LI to create the script link, and there are better ways to align the link
beyond using 10x not-breaking spaces...
Thank you
Rodney Pearson
Lovaquero
|
|
|
| Author: | lovaquero | | Posted: | Aug 20, 2014 15:13 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 57 times | | Topic: | Suggestions | |
|
| In Suggestions, QCBricks writes:
| |
Sadly, the long line of complaints about every little thing BL has done (from
the proposed logo changes on) impacts your timing. If you truly intended to
pass this information on in a serious manner to BL, you would have done that
by going through the Help Desk rather than posting it here to be hijacked by
the "BL is the worst thing ever" crowd.
You aren't new to the forum and I am sure you read it from time to time.
You had to know that your post would do nothing but embolden those in the BL
does everything wrong crowd.
I also don't see that either Jim or I "belittled" anyone. What Jim said
is exactly true. Everyone shouted for change, then they got a change and are
now doing nothing but shouting for the changes to be rolled back.
Be careful what you wish for...
Scott
|
Oh, I agree. On all points. I am with you on just about all of it.
And yes, I knew full well what would happen with this thread. Better it be focused
in one place than in every thread (even though I am guilty of that too). Hence,
my original response to Jim. What I wanted to originally post was most
definately what you are advocating against...luckily my wife got to me first...
As far as passing along information, well, I've tried the official route
and received no response at all. Which is OK, if not somewhat frustrating.
Bricklink has their own agenda and reasoning. I can live with that. I struggle
with actions not matching words. Bricklink has an image problem in that arena.
What Jim said is true. He also chose to take my post in a way that it was clearly
not intended. Your comment on logic, while quoting mine and Jim's post comes
across as belittlement in my book. I guess that is just the dangers of a forum.
I must needs grow thicker skin... /shrugs
|
|
| Author: | lovaquero | | Posted: | Aug 20, 2014 14:58 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 57 times | | Topic: | Suggestions | |
|
| In Suggestions, QCBricks writes:
| |
As I said in my reply to Steve...this issue may be the one that deserves the
complaints,...
|
Which 'issue' do you refer to? The issue of my OP was in no way directed
at the items you have enumerated. I was addressing the process, or lack
therof. Perhaps part of the challenge is that there are two different conversations
going on:
1 - Frustration over the process by which Bricklink releases updates (my
original post and point)
2 - Frustration over the changes made by Bricklink (that point you appear
to be addressing)
|
|
| Author: | lovaquero | | Posted: | Aug 20, 2014 14:50 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 54 times | | Topic: | Suggestions | |
|
| Jim & Scott -
If your replies are designed to parady certain behaviors on the forum, I commend
you. Otherwise you have mischaracterized what I said & suggested.
I have no problem whatsoever with the changes being made to Bricklink. I welcome
a great many of them. I question some, and scratch my head over others, but
overall it is good. It is the delivery and execution that I am addressing.
There is a time and a place when 'complaining' - making a statement that
a situation is unsatisfactory or unacceptable - is valid and acceptable.
Belittling others for voicing a dissatisfaction is no better than the behavior
it attempts to decry.
~Rodney
|
|
| Author: | lovaquero | | Posted: | Aug 20, 2014 13:24 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 53 times | | Topic: | Suggestions | |
|
| In Suggestions, pumbaugh writes:
...who has been very quite today. Not that I blame him. These sorts of things
should NOT have made it past his - or his teams' - review. I'd also want
to keep a low profile amongst the BL forum crowd in the same sitation...
|
|
| Author: | lovaquero | | Posted: | Aug 20, 2014 12:27 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 56 times | | Topic: | Suggestions | |
|
| In Suggestions, rtzx9r writes:
| |
Of course this comes with a cost, and likely BL is not performing this due to
this issue. I guess we can live with bugs, or pay more in fees. We can't
have both unfortunately.
|
Yes, the cost is quite high. Then again, based on what has been shared, BL has
invested in a good sized development and customer service team. Perhaps those
should be cut in half and replaced with a quality assurance and testing team?
|
|
| Author: | lovaquero | | Posted: | Aug 20, 2014 12:22 | | Subject: | Re: BL Development Team: Test before rollout! | | Viewed: | 61 times | | Topic: | Suggestions | |
|
| | |
Thats a nice pitchfork and torch you carry.
Can you elaborate on what some of these horrible bad things are that BL has recently
done that now make it impossible for anyone to ever use BL again?
|
You should have seen the previous version that my more level-headed wife insist
that I dispose of...
No need to elaborate on the horrible, bad things. Go to http://www.bricklink.com/messageList.asp?nID=&v=c&max=20&mTP=Y
and read the titles. BL devs screwed up. It happens.
My point isn't the changes, it is how they are rolled out. There is clearly
very little testing being performed on these changes before they are pushed live.
What testing that is performed is clearly inadequate.
Would you expect these kind of issues to persist, and occur again and again,
on one of the more major e-tailers? How about your bank web portal? Or your
network security updates? Perhaps it is acceptable with the software that makes
it possible for a modern vehicle to function?
My expectations are already quite high (based on my job responsibilities), and
I refuse to lower them for this website (or any other), based on all the PR that
has been feed to us regarding the state of BL, the dedication of the new owner,
the quality of the BL team, and the resources being thrown at BL.
In short, expectations - those set by BL itself - are not being met. Let's
start with making sure that what changes are made are done correctly with as
little interruption as possible.
|
|
| Author: | lovaquero | | Posted: | Aug 20, 2014 10:19 | | Subject: | BL Development Team: Test before rollout! | | Viewed: | 462 times | | Topic: | Suggestions | | Status: | Discarded | |
|
| Bricklink World Class Programming & Customer Serivce team -
Test before release. This concept is not hard. Perhaps in your eagerness to
pacify the crowd with pitchforks and torches you have forgotten it. Perhaps you
may just not know. Here is how you do it:
For EACH (individual) change to Bricklink:
-----------------------------------------
#1 - Scope your change to know its impact
#2 - Write your test plan to match the requirements for the change
#3 - Recognize that there are at least three (3) internet browsers to support:
Chrome, Firefox & Internet Explorer (IE)
#4 - Make sure that the test plan fails before any change is made
#5 - Implement the change, and only that change, in a development environment
#6 - Execute the test plan (in an isolated environement that matches the live
environment) for Chrome, Firefox and IE
#7 - Repeat steps 5-6 until the test plan passes for all three (3) browsers
#8* - Run the full test plan on the ENTIRE site to ensure everything still works
#9 - If anything fails, return to step #1 and repeat
#10 - Release the change to the live site.
(* Bricklink is written with ancient software that has so many dependencies,
querks, gotchas and 'hidden' features that it is impossible to know what
a change will do to seemingly unrelated features. That is why the software used
to run Bricklink is no longer used nor even supported, not even by the company
that originally created the software...)
Your new mantra must be: "test! Test! TEST! And then test it again!"
Any modern development team worth being paid - especially one that performs
web development - knows this.
Regards,
Rodney
Software Systems Engineer
Solution Infrastructure - Guidance & Machine Automation
John Deere Intelligent Solution Group
|
|
| Author: | lovaquero | | Posted: | Aug 20, 2014 09:42 | | Subject: | Re: Localization settings | | Viewed: | 37 times | | Topic: | Suggestions | |
|
| | Where is the +1 button? THIS suggestion all the way. |
| Author: | lovaquero | | Posted: | Aug 7, 2014 11:41 | | Subject: | Re: Forum block goes both ways. | | Viewed: | 39 times | | Topic: | Suggestions | |
|
| I have to vote NO.
Really, anyone that gets into a forum war-of-words with another gets everything
that is coming to them.
One of the joys of growing up is learning when to and when NOT to engage someone,
as well as when to disengage.
In Suggestions, Lonely_Brick_OH writes:
| | I would like to suggest for Brick Link 2.0 that the forum block goes both ways.
Not only can you not see what the other person is posting, but they cannot see
your posts either.
I believe that will solve a lot of disputes.
Thank you.
|
|
|
| Author: | lovaquero | | Posted: | May 9, 2014 10:17 | | Subject: | Re: Implement a Validation Team for BL Changes | | Viewed: | 38 times | | Topic: | Suggestions | |
|
| In Suggestions, cs_amanda writes:
| | I wanted to let you know that I forwarded this suggestion on for consideration.
Thanks
Amanda
CS Team
|
Thank you Amanda.
|
|
| Author: | lovaquero | | Posted: | May 8, 2014 11:16 | | Subject: | Implement a Validation Team for BL Changes | | Viewed: | 276 times | | Topic: | Suggestions | | Status: | Already Exists | |
|
| SUGGESTION:
BL development team needs to implement a validation process to validate any changes
made to BL prior to live roleout. This should include the use of personas,
a focus test team, and potential involvement of community members.
This is common industry practice for any software development team, and is needed
if BL is operating in a Scrum/Agile development fashion (which appears to be
the case).
--------------------------------------
I REALLY like how BL is finally starting to implement some of the
suggestions from the BL community. Many of these changes are positive, and I
commend BL for starting to take action to improve the website.
Having said that, too many of the changes are seemingly being implemented without
any sort of validation or consideration to what the impact will be. It is
like the developers working on the site have no process to prove-out the changes
prior making those changes live.
Case In Point:
A new 'color' box was added to order line-items to help with color-picked
parts. This was implemented in HTML as a 'background' color. On-screen
this looks good, but to print you must enable background printing. This, in
turn, caused the entire page to print, which was too much. So BL removed all
background color, made the order page completely white (even overriding default
browser settings) and added a thick black border around the order.
Problems with this:
(1) To print the color boxes one still needs to change print settings specific
to BL. Then change back the settings for other websites.
(2) If you DO print orders, you now have roughly doubled your black ink
comsumption due to the unneeded black border
(3) If you DO NOT print orders, you are blinded by the glaring order page.
This is bad for your eyes and bad for your monoitor.
(4) You cannot override the layout/color scheme due to webpage implementation
All of these problems should have been identified and addresses prior to the
constant changes being implemented. A proper validation process would have identified
the root problem (i.e. how the color boxes were implemented) and created a solution
to fix the root problem rather then its symptoms (i.e. unable to print the color
boxes). This would have resulted in the issue being identified and corrected
(i.e. implement the boxes differently) before the new feature was mode live on
the website.
|
|
Next Page: 5 More | 10 More | 25 More | 50 More | 100 More
|
USA, Indiana
)
)
)
)