• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

hyperlinks in custom pageset

N

Nayabk

Guest
Hello,
We're trying to insert hyperlinks into a pageset. These are relative to the page. E.g in a home page we're inserting a hyperlink with href = "/Login/Login.aspx" and a few more to other pages that we've created.

The problem is that after saving this page, the href get changed to href="http://sb.XXYZZZ.com:2006/Admin/ComponentsMgmt/Login/Login.aspx". When a user tries to use this pageset, the URL is incorrect and points to a folder that doesn't exist.

Is this a bug? If it is please advise on a workaround and when it can be fixed.
 
In regards to your hyperlinks, i've had the same thing happen to me, all the time.
I dont know what is causing it, but possibly it might be because your using the default
publishing domain of domain.com/site instead of just domain.com/

I wish I could be more help to you. If you find out what causes this, please write back.

Thanks!
 
Hello,
Can someone from SWSOFT please answer the question. We desperately need to enter relative URL's in our templates. THanks.
 
Can you please describe in details how to reproduce this issue on latest Sitebuilder 4.2 version?
I tried to reproduce it at http://sitebuilder4.win.demo.parallels.com/ Demo server and had no luck.
We had this issue in Sitebuilder 3.x and 4.0 and it was fixed in 4.1 or 4.2. Please check and if in 4.2 it works fine, please upgrade your Sitebuilder installation.
 
Back
Top