Welcome to the IBM Connections Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by the IBM Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events, please visit our IBM Connections page.


Pasting a Wiki URL into textbox.io is resolving the URL name as "Welcome to Wikis" instead of Wiki title.


Using ephox 3.5.1.14 and 3.7.0.10 there is an issue with pasting wiki link into the textbox.io.
If you copy any Wiki URL and paste it into textbox.io it will automatically turn into "Welcome to Wikis". Which is misleading. Instead of "welcome..." it should be the title of the wiki where the link is pointig to or no change at all, so the user can choose themselves how they call the link and have no need to press ctrl+Z to avoid the "welcome to IBM Connections/wiki" as it looks like link to a homepage and not the intended page.

Steps to reproduce.

1 - Create a Wiki1 and Wiki2 in IBM Connections. Copy Wiki 1 URL.
2 - Edit Wiki2 page and paste Wiki 1 URL into the RIch text tab of the textbox.io.
3 - The URL will change to: Welcome to Wikis.
4 - If you press ctrl z the URL changes to its original format.

 

 

-------------

The desired outcome is to show the wiki title, not only ''welcome to wikis''.

 

------------

 

Workaround:

 

Instead of pasting the link into the Wiki's body, there is an option available to paste the Wiki title using textbox.io:

Go to "Insert Link" option on the menu bar - Wiki page link.

 

You can select the Wiki and its title will be displayed instead of welcome to wikis.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 13 2018
  • Future consideration
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    08 Jan 15:01

     We has been told that this issue is fixed/implemented in 6.0CR3. However it was not. Do we have any new schedule when this will be included in the product?