Skip to main content
/

Site Navigation

Your Account

Choose Language

This is Feedback, not a question] Inconsistency when editing intro

I just edited the introduction of a procedure, to add an item to the tools list.

As the item I added is optional, I intended to take advantage of the Notes field to make a statement like "recommended for habitual fixers."

Problem

While this field gets saved, and while it previews OK, this field does not actually display in the saved page.

It appears this field displays in the saved page only when the added tool is not linked to the iFixit Store.

Suggestion

If this is by design, then I suggest correcting the editing page code to not display this field when a store link exists for the item being edited (or at least add a note when the field is visible for editing.)

Workaround

I worked around this issue by leaving the Notes field empty in the tools list without qualification, and I added a comment in the introduction text.

</2ยข>

Thanks.

Answered! View the answer I have this problem too

Is this a good question?

Score 1
Add a comment

2 Answers

Chosen Solution

Interesting find! We'll look into making this more straightforward. Thanks for your post!

Was this answer helpful?

Score 2
Add a comment

I know what feature you're talking about. Personally, I haven't used it in about a year so (probably around 2-3 years), so what I think happened is I'm not the only person who stopped using it. Eventually, the feature became redundant so when the new UI was being designed, it wasn't a priority because it did not see a lot of use.

To be fair, it still may be useful in a few guides. In my guide on the L755 hard drive replacement, I had to use it to designate that you need a 7mm-9.5mm adapter for modern drives due to the L755's chassis being designed for 9.5mm drives. This note was no longer visible with the new guide format, but I was able to work around it.

What I did as a workaround was I put the note I had by the adapter in the Intro of the guide in bold, so it is not glanced over. It's not what I used before and I did have to adjust for it, but I corrected it with one single change to the guide. It wasn't hard to work around.

Was this answer helpful?

Score 1

2 Comments:

RIght, NIck - it's not hard to work around; it just offers a blind path for folks to learn about.

Ideally, when a develop changes a field's display behavior to be conditional, they should either add a note about the conditional display, or -- especially in an input-savvy form like this -- hide the Note field (immediately, on the input form) when the user provides a tool link to the iFixit store.

by

I picked up that I was going to need a solution when I was testing the new UI. That's why I knew how to work around it and was not bothered by the removal. I ended up realizing I didn't use it enough to worry about the omission when I was seeing how the new UI worked. My concerns were how was the UI going to change, and what formatting changes was I going to have to make to my guides if it comes up. I needed to know that for future guides and new guides. There's definetly a little bit of a learning curve. However, once I figured out what I need to do I have been able to make writing any future guides quicker, as there is no trial and error checks.

I do think they should have done more to make it easy to pick up; I picked up because I knew ahead of time. They should remove the option to add a note, since it does not support extra notes anymore. That should be good enough to prevent confusion.

by

Add a comment

Add your answer

Bass Clef will be eternally grateful.