'Copy Link' menu option gives wrong link.

[Andrew Neil]

I have copied this link from the post “STM32CubeIDE 2.2.0 released”:

https://community.st.com/stm32cubeide%2Dmcus%2D28/stm32cubeide%2D2%2D2%2D0%2Dreleased%2D166532

 

But that link actually goes to:

Text of the URL (with the https prefix removed, to stop the forum linkifying it):

community.st.com/stm32-mcus-embedded-software-32/how-to-send-int-values-efficiently-through-cdc-usb-39682?postid=166532#post166532

Which does, in fact have the same ?postid=166532#post166532 as the other link!

[Andrew Neil]

The problem was noticed by @mALLEm in this thread:

 

In that thread, note that the forum gets the correct thread title in its linkification:

 

even though the link actually goes to a different thread!

 

Also, why did the URL not linkify properly for this thread:

 

[mƎALLEm]

Did you copy the link with this option?

Because I got different link with “Copy link””: 

 

https://community.st.com/stm32-mpus-software-development-tools-138/stm32cubeide-2-2-0-released-166535

[Andrew Neil]

Did you copy the link with this option?

Yes, that’s the one.

 

 I got different link: 

That’s the one for MPUs ...

[mƎALLEm]

Strange.. 

I did use the same option and it provided me the right link!

[mƎALLEm]

Just did some tests.

The behavior seems to occur on old posts (paraphs before the migration date May 22 - Need to confirm). Copying new posts link seem to be working well.

For example this post / created 5 months ago. The link copied from the browser URL: 

By copying the link:

Seems to go here: 

 

[Andrew Neil]

The behavior seems to occur on old posts (paraphs before the migration date May 22 - Need to confirm).

Unfortunately, that seems to include all the Community Guidelines; eg, see:

 

[Lina_DABASINSKAITE]

Hi ​@Andrew Neil , 

Thanks for the reporting this. We noticed the same issue yesterday and our vendor is working on a fix already.

We will notify once it’s resolved. 

Regards,
Lina

[shrinivas96]

When trying to copy the link to a question, by clicking on the three dots on the top right of the question box, the link you get is nearly the same as the URL you can already see in your browser, but leads to a completely different posts’ comment section once pasted in the browser, or any other document. For example, I was on this post (top link), and its corresponding link that appears when I paste (bottom link):

 - https://community.st.com/stm32cubemx-mcus-29/how-to-customize-your-stm32cubemx-generated-cmake-project-159569

 - https://community.st.com/stm32cubemx-mcus-29/how-to-customize-your-stm32cubemx-generated-cmake-project-159569

 

Seems both are nearly the same. Click on bottom link (or paste it into your browser), and you are brought to a completely different post. Tired this also with other questions. Does not happen with replies to posts though. Of course I can just copy the URL shown in the browser’s address tab, but I thought this was peculiar behaviour.

[Lina_DABASINSKAITE]

Hi ​@shrinivas96 , I merged your question with the ongoing discussion on the subject. 

We are aware of the issue and are waiting on a fix from our vendor. 

Apologies for this temporary inconvenience. 

Kind regards,
Lina

[Lina_DABASINSKAITE]

Hi ​@Andrew Neil , ​@shrinivas96 , 

The Copy Link issues have been fixed. Please check again and let me know how it works for you. 

CC team: ​@Laurids_PETERSEN , ​@Maxime_MARCHETTO1 

[Andrew Neil]

The link in my OP:

I have copied this link from the post “STM32CubeIDE 2.2.0 released”:

https://community.st.com/stm32cubeide%2Dmcus%2D28/stm32cubeide%2D2%2D2%2D0%2Dreleased%2D166532

Still goes to the wrong place.

 

But if I go back to the STM32CubeIDE 2.2.0 released thread and now do a ‘Copy link’, the resulting link does seem to be correct:

https://community.st.com/stm32cubeide%2Dmcus%2D28/stm32cubeide%2D2%2D2%2D0%2Dreleased%2D166532?postid=743007#post743007
 

I’ll try it on another:

 

Edit: yes, that’s also working.

[Lina_DABASINSKAITE]

Hi ​@Andrew Neil ,

Yes, I have reported this back to the support team as I noticed the already generated links remained wrong and the solution seems to apply only for the new attempts.