Skip to main content
/

Site Navigation

Your Account

Choose Language

Major bug when editing guides

Since I started getting the Linux 2007/2008-2012 guide in a state where it can be fixed and brought back, I have noticed a bug. If I edit it on my phone and then move to my computer, I have to deal with a different character limit in terms to what I can type on the 2 platforms. On my phone, I have the full limit and on my computer, I lose 6-10 characters, or more. On average, it's within 6-10 characters.

How I got hit with this bug:

  • I did some work on the intro of the guide on my phone last night. The phone was using the iFixit app. My phones are a N5 (2013) and a G4. This happened on the N5 and the N5 has version 2.9.2 on it. It's probably older, which may have led to this issue.
  • The problem this bug causes is it messes up how I work on these guides. I can do a small edit on my phone but anything substantial requires a physical keyboard be used. I can't type long form on a phone. When I move to a PC to do long form, this issue comes up.
  • I initially edited the introduction on my computer, and then tweaked it on my phone. This came up when I tweaked it on my phone then did edits on my laptop this issue came up.

Anyway, here's a screenshot:

Block Image

Hopefully I can fix this by flooding my phone with one character to "max" the phone out and then come back to the PC version and find the issue gone. If I try this I'll report on the results.

This does not fix the problem. Copying and pasting the full text doesn't fix it either. The most it does is cut off details you had before, since you are dealing with different character limitations.

Bug update 2

This is even happening on guides I never edited on my phone. See the attached picture:

Block Image

Answered! View the answer I have this problem too

Is this a good question?

Score 0
15 Comments

Hi Nick, could you add any more detail about this bug? I wasn't able to figure out what the problem is from your description. I hope we can resolve this issue!

by

So I edited the original version of the Linux configuration guide on my phone 5 days ago, as the publishing date says on the iFixit app, which is version 2.9.2, if that helps. I only did a small edit on my phone because I can't type long form on a phone. I need to use a real keyboard so I had some edits in mind for when I could get back to a real computer. When I get back to a real computer and not my phone, I did the edits to find the character count on my phone is off on my computer when I set up my 2007/2008-2012 hardware standards. I had 24 left, before I hit the real limit. That one was off 24 so I had to work around that best I reasonably can.

by

The second screenshot is 2013-present, which I am still deciding on standards for (which I may or may not let people chime in here; they're not up there and I accounted for the improvements in newer lower end hardware within reason) I ran into the same issue. Both of these are in the Introduction from what I can tell, and hopefully limited to that area. I know I never edited this on my phone, because I am scaling down on my 2007(desktops)/2008(laptops)-2012 guide and pulling from that guide so I do not have to write as much from scratch. Once I scale down, THEN I might start from my phone because it's a simple copy/paste job at that point.

I hope that information helps. It's probably something to do with the app messing the website counter up, at least from what I can tell. The original's counter is still broken and I do not know how to fix it without making 24+ useless edits with garbage. I would rather not do this.

by

What I tried so far is to flood the app and nuke it from a computer with no luck, copy/paste cost me details so I discarded that attempt. Maxing out on the phone didn't fix it either.

by

So you were experiencing different limits on different platforms?

by

Show 10 more comments

Add a comment

1 Answer

Chosen Solution

@nick, thanks again for your feedback. We have made changes to the website, and I think you'll find that the issue you were having before has been solved. Please, feel free, as always, to let us know what you think!

Was this answer helpful?

Score 1

2 Comments:

I tested it in Windows where I had the issue and the issue is confirmed to be fixed.

by

Glad to hear it!

by

Add a comment

Add your answer

Nick will be eternally grateful.