Old url markup not migrated to new forum

I still get those types of notifications too.
And YES they often refer to old or misleading URL's
Even if the post is "closed" you can still edit your posts and re-do the links to a better URL or include additional material.

Thanks for the report! I triggered a rebuild of the post and the forum software was able to render the markup correctly now.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.

I still find links which are not rendered correctly.
Sometimes I just correct them, but I still hope this will be solved finally and for ever one day...

Thanks for the report! I triggered a rebuild of those posts and the forum software was able to render the markup correctly now.

on "all" forum posts or just these 5?

Just those five. I understand very well what you want, but I can't provide that. So we have to make the best of a bad situation. That means I am happy to fix broken posts as they are reported, and those with post edit privileges are also welcome to do so directly.

I can edit my post, I'm just getting tired of doing it. I roughly remember the bug report from last year. It is marked as solved, but I don't have the impression that it is really solved and I have no idea how I can support that one guy in the background who should have the power to solve that issue finally.

The bug is fixed, but that fix doesn't apply to the posts that were created before the time of the fix, only to posts made after the time of the fix, or old posts that are rebuilt (AKA "rebaked") after the time of the fix.

There is information regarding a universal fix in post #13:

So the naive solution of rebaking all the millions of posts on the forum has been ruled out by someone who is very knowledgeable on the subject of Discourse-based forum.

The possible alternative solution would be to write a script that identifies all the broken posts, and does a targeted rebakes only those posts. It appears that the query used by the previous script was not effective at finding all the broken posts because we are still finding them even now.

I would be interested if that search string is able find this post:

and what the data in the database looks like currently and after it was "rendered manually".

by the way:
here I have an example with identical URL, one with a "line break" and the other one as "one liner" - neither get rendered correctly:

two lines:

one line:

More?

I speculate that these requests coming from the Arduino forum:

https://werner.rothschopf.net/microcontroller/202109_millis_larson_scanner_en.htm[/url]
https://werner.rothschopf.net/microcontroller/202011_arduino_webserver_optimieren.htm[/url]
https://werner.rothschopf.net/microcontroller/202201_a02yyuw_ultrasonic_sensor_en.htm[/url]
https://werner.rothschopf.net/microcontroller/202102_arduino_wettersensoren.htm[/url]
https://werner.rothschopf.net/202009_iot_webserver_intro.htm[/url]
https://werner.rothschopf.net/202010_arduino_webserver_favicon_en.htm[/url]
https://werner.rothschopf.net/microcontroller/202102_arduino_antennenschalter.htm[/url]
https://werner.rothschopf.net/microcontroller/202108_arduino_webserver_ntp_sd_en.htm[/url]


https://werner.rothschopf.net/microcontroller/202203_tools_button_en.htm[/url]
https://werner.rothschopf.net/202009_arduino_liquid_crystal_intro.htm/
https://werner.rothschopf.net/microcontroller/202204_atorch_dt24hd_power_sensor_en.htm[/url]
https://werner.rothschopf.net/201809_arduino_esp8266_server_client_3.htm[/url]
https://werner.rothschopf.net/202003_arduino_retriggerbares_nachlaufrelais.htm[/url]
https://werner.rothschopf.net/microcontroller/202108_esp8266_esp12f_relay_x8_en.htm[/url]

I was able to find those and quite a few others with this SQL query:

SELECT CONCAT('https://forum.arduino.cc/t/', topic_id, '/', post_number) FROM posts
INNER JOIN topics ON posts.topic_id = topics.id
WHERE archetype = 'regular' AND baked_at < '2023-04-26T00:00:00.000Z' AND posts.deleted_at IS NULL AND cooked LIKE '%\[url\]%%'
ORDER BY topic_id, post_number ASC

of course it also has a lot of false positives for posts where the tags occur in code blocks, such as when forum members are instructing others in how to make links.

I rebaked all those posts so hopefully they are all fixed now.

I also had a run at the results of the query searching for occurrences of [/url]. That one includes all the times when the forum members made an error in the tag syntax, which can't be fixed through rebaking so instead requires manually correcting the markup. There are hundreds of those which I have not fixed.

1 Like

thank you @pert .