urls in search results are not clickable links

[timo11]

It is necessary to open a detail view and copy and paste urls into new browser tabs to view the referenced data.

[timo11]

If 'linkify' is true for a field definition (in resources/config/fldmodel.json) then urls contained in that field will be displayed as hrefs in grids and forms. Referenced pages will open in new browser tabs.

[benanhalt]

Just as an aside, in Chrome at least if you select a URL and right-click there is an option to "Go to http://whatever.it.is" even if it is not a link.

[timo11]

But urls can't be selected in table displays of results.

[benanhalt]

Not that it matters since you added this, but if you can't select them, then how could you copy and paste them?

[timo11]

The first installment of this feature has been on the master branch and 'released' since 2018/6/20

[timo11]

Not that it matters since you added this, but if you can't select them, then how could you copy and paste them?

You have to open a detail view.

[maxpatiiuk]

make them be clickable by default

[maxpatiiuk]

Does not seem to work
Links are not clickable regardless of the linkify defaultvalue
On the detail view every field's data is inside an input, yet it is not supposed to be editable, which does not makes sense #44. That may be the cause of this issue
Am I supposed to change anything else for links to begin working?

I did git pull so my local wp must be up to date

[timo11]

Does it work if you set linkify to true in app/resources/config/fldmodel.json?

[maxpatiiuk]

It was not set for any of the fields
I added it at the end like this:

and then did everything according to README.md starting from step 4

Still does not seem to work:

[timo11]

Default is not working, but it works for me when I set linkify in fldmodel.json

[timo11]

Linkify should be true by default for web portals exported as of commit 52c088b to specify6 repo for specify6/issues/688

[maxpatiiuk]

I will reinstall WP on a clean Ubuntu install and will change the config file before running the make command. Hopefully, that will make links work

Also, is there a case when the user would want links to be not clickable? Performance difference?

[maxpatiiuk]

It works!

Partially
webportal-installer/PortalApp/resources/config/fldmodel.json file does not seem to affect links
Also, PortalApp/app/model/FieldDefModel.js does not seem to affect links

flds.json file works well
Though, I initially added the "linkify":"true" for every line and that resulted in Loading... when searching for data. I waited for 10 sec and canceled loading

Just saying that making that option be on for every column is very decremental for performance. I would suppose that it runs regex on every row in that case. It would be wise to firsty check if the string contains http and only after that run regex on it

(I had 165641 record on 3313 pages with about 30 cols

Making links be enabled only for one col in flds.json worked well and performance
was not bad

[timo11]

the file that needs to be edited is fldmodel.json in resources/config either in build/html/[core]/ or build/cores/[core]/webapp, depending which folder is installed to the http server. After installation changes to a portal's settings need to be made to the fieldmodel.json file in the installed portal app.

All fields in fieldmodel.json (and flds.json) have linkify set to true as of 3/23.

Filtering for http would eliminate links formed w/o http like ku.edu, xyz.org, www.frdc.co.uk etc.

I think we should automatically enable linkify for weblinks when the build web link pref is on, and make it false otherwise.

[timo11]

Seems that blindly setting linkify to true for all fields causes the portal to hang forever when linkify is executed for non-text fields. specify6/issues/688 is being reworked.