Hello,

I mentioned this strange behavior at least on the Features-blocks.

How to reproduce:

1. Add a Feature-block (e.g. Feature 10)
2. Add a Feature-item
3. Select "Link Type" -> "Custom Link" and add # as target
4. Save the page
5. Switch "Link Type" to "Page Link" and select a page
6. Save the page
7. On the frontend, the # is still available.

Workaround: Empty # from "Custom Link" and then switch to "Page Link".

roman30845 said:

Hello,

I mentioned this strange behavior at least on the Features-blocks.

How to reproduce:

1. Add a Feature-block (e.g. Feature 10)
2. Add a Feature-item
3. Select "Link Type" -> "Custom Link" and add # as target
4. Save the page
5. Switch "Link Type" to "Page Link" and select a page
6. Save the page
7. On the frontend, the # is still available.

Workaround: Empty # from "Custom Link" and then switch to "Page Link".

Hello Roman!
Yes this is because you fill both fields with data custom link field and also page link field. The if statement inside .htm block check first if there is a custom link entered and if not selects page link. You have to clear custom link to be able to use page link.

There are methods to change that behavior of course but i didn't implement them to keep the code lighter and keep fields more friendly.

Do you believe that this is a major issue that needs to be addressed?

Hi Charis,

for me it's just not expected behavior, as I actually choose the type of the link. If the logical expression comes to another result, I think it's not what a user would expect.