[wp-trac] [WordPress Trac] #59117: The WORST of ALL Bugs (Version 6.3)

[WordPress Trac]

#59117: The WORST of ALL Bugs (Version 6.3)
--------------------------+-----------------------------
 Reporter:  atutrabajo    |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  6.3
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Dear friends, good afternoon. I know that, at 1st. Vista may believe that,
 this is not the right place to write this. But give me a few minutes and I
 will (de)show you that it is.
 To gain time, below is the link to the ticket in which the subject was
 discussed;
 https://wordpress.org/support/topic/huge-error-for-my-site-when-upgrading-
 to-6-3/page/2/#post-16969028
 If they READ it all (That is, the 2 flaps that said ticket includes), they
 will realize (I hope) that…
 1) It is a problem that you generated ONLY in the latest version 6.3
 2) NONE of the solutions provided by v/collaborator WORKED.
 3) They caused me (and they cause me) MANY inconveniences (even LEGAL)

 To summarize (and in case you don't feel like reading so much, heh:)…
 a) I have been designing my site on v/platform for +3 years. Ergo…
 b) There is NO way for ME to implement the suggested fixes.
 And that is why…
 c) I am NOT going to update WordPress to its latest version (6.3) until
 this is resolved.

 So, for finishing…
 - Why do I say that it is a problem generated by you? Simple.
 Because until version 6.2 I DID NOT have it.
 - Why do I think they should fix it as soon as possible?
 Because if you look, in the same forum, there are MANY similar claims in
 THAT sense.
 And finally…
 Why do I think this is the WORST security bug WordPress can have? Easy.
 Because if it is not solved (FAST) I (and probably MANY more), will leave
 our installation with the previous version (6.2.2).
 And – if so – as I'm sure you know, I'll be left open to whatever attacks
 you guys have sought to address with your latest version (6.3).
 And then? So, if my hosting does not suspend me (Potential Legal Problem
 that I mentioned before), it could even affect other sites that are within
 my hosting (which is obviously shared, so I can NOT afford the "luxury" of
 anything else ).
 Ergo. If many sites (like mine) do NOT update to 6.3 and like me, they
 share their hostings, a problem that is generated in one, could affect ALL
 of them.

 Having said that…
 If you keep track of these tickets, you'll see that in the +3 years I've
 been using WordPress, there was NEVER an entry to this section, which is
 said to be for…
 …”suggest improvements and report bugs in WordPress”…

 But it seemed necessary to me because, from what I see, SEVERAL days have
 passed since I created the ticket whose link I attached and, we did NOT
 find the solution.
 And, what is worse, I do NOT think you will find them in the forums. Why?
 Simple.
 Because if you READ the ticket in question in detail, you will see that
 the ONLY one in a position to provide a solution is WordPress itself!

 That's all for now (I hope you understand).

 I await your comments.

 Thanks in advance.

 Greetings.
 PS: As I already mentioned in the ticket mentioned above, what will NOT
 happen is that…
 I have to rewrite my ENTIRE site (+120 thousand words) for a problem that
 I did NOT create!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/59117>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform