@Interlated Thanks for the reminder. composer show is more readable that directly poking through the lockfile.

What does EXPLAIN tell you about the query?

This code example isn't really helpful. Can you explain what code it is, where it goes, and how it solves the problem for "when a user is editing or creating a node"? Thanks.

From that screenshot, I am assuming that is Drupal 7 + Date module. IIRC the D7 Date module stores both the UTC offset and the IANA timezone name with each value. I highly suspect that there is a mismatch here, and potentially system/server zone misconfiguration, resulting in the timezone rules for DST not being applied properly. Unfortunately, a bunch of wrong things can add up to the date being displayed properly until a DST switch.

I would write this as an answer, but I think this is a problem with your Feeds import and not the Views formatter. If you look at the raw data in the database, is it correct? I suspect you have a bad timezone translation or a double timezone translation going on during the import. I think you may need a tamper.

Do you have any errors on admin/reports/status ?

Confused by your screenshots. The first looks like a Javascript popup (from the date_popup module?). The second looks like the native Chrome date picker. If you do <input type="date"> then you will always get the native date picker. You need to do <input type="text"> if you want to override this behavior. But, I am not familiar with the date_popup to know how to integrate it with Form API.

Noticed a bunch of retags on this. Please note that version tags should be used only for questions that apply to a version only, not to merely say what version a site is using.

What version of Drupal? 7 vs 8 makes a big difference here.

I'm not sure if this is accurate. I am pretty sure that all mod_write rules happen before mod_alias rules, because the modules execute in that order, and not by the order of the rules in the file. I have run into that issue before when mixing Redirect and Rewrite.

This sounds like the cacheable metadata from the content on the route isn't being set properly, or something is smashing it.

As an aside, redirecting from a 404 may may cause weirdness w/ spiders (eg, Google), especially if you 3xx to another domain.

Not 100% sure, but you may be able to create a Text Format that only allows some inline elements, like <b>, <i>, <u>, and not the block level ones, and don't convert newlines to <p>.