Extra field link has a default value of http:// which is problematic about k2

[kavadas]

Hi. The field is indeed populated but you should not get the value on the front-end since there is a check for empty links ( http:// values ). What version of K2 are you using?

I am using 2.6.7, you can see here I created an empty article :

http://dcv3.ponnuki.net/index.php/canyoning/buecher

and it list all the http:// (it's in a list view)

[kavadas]

We have already implemented a fix. Can you please use the development version and provide some feedback on this? The development version can be found at http://getk2.org/assets/get/

http://dcv3.ponnuki.net/index.php/canyoning/buecher

same story, did I had to flush any cache or anything like that, when upgrading the k2 extension to the dev version?

[kavadas]

The output you are viewing is coming from the filter module you have used. This is not part of K2. K2 pages ( and modules ) don't have this issue.

Right, but shouldn't the field be empty by default in order to play nice with other module? And if you scroll a bit lower you get all the field showing up in a normal display too.

So an easy way to go around that limitation is to remove the default value from the database, it probably get put back in the database when I would make change to these extra field, but meanwhile it helps a lot in the entry of new information.

I still think this is a weird behavior that I cannot define the default value I want on a link extra field.

[betweenbrain]

I do agree that this can be problematic. I ran into a similar situation myself. To me,it makes sense to leave it blank, and maybe set this portion in the default view so it can be overriden with a sub-template.

[kavadas]

I am reopening this. Maybe the best solution would be to remove completely the prefix.

[betweenbrain]

I think that's the best solution. There may even be situations where the use wants relative inks, or to even enforce use a CDN. This would allow that to happen much more easily.

+1

[kavadas]

I applied a quick fix (38c3965). The prefix is now only applied when a value is entered. We need to think a bit more about the total removal of the prefix.

[betweenbrain]

Complete removal could be a backwards compatibility issue, correct?

[kavadas]

@betweenbrain No i don't think so. I just need to talk with the rest of the team for that first.