-
Notifications
You must be signed in to change notification settings - Fork 746
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sitemap priority 0 when adding a single page #3081
Comments
The Persona Bar is defaulting to 0 and I can reproduce in 9.3.0 RC2 too. |
one more thing. |
This needs to be retested, I think I put the "pull request submitted" by mistake on this one, I cannot find that PR now... |
Just had a minute to test and this is still an issue in 9.4.1 |
Still an issue in 9.8.0 |
I can imagine that this is difficult to fix in API. If it is easier to fix it (at least temporarely) in the database, that would do. To explain the magnitude of the issue: |
@schotman commented on Fri Mar 01 2019
Description of bug
When using the add a new page function in the pages dialog the SiteMapPriority is not set in the dialog and defaults to 0 in the database
Steps to reproduce
List the steps to reproduce the behavior:
Current result
SiteMapPriority = 0
Expected result
SiteMapPriority defaults to 0.5 (as it is when you add multiple pages)
Screenshots
seems clear
Error log
no error
Affected version
Affected browser
not dependant of browser
@sleupold commented on Fri Mar 01 2019
IMO this should be fixed in DNN API code, not the database default value.
@Timo-Breumelhof commented on Fri Mar 01 2019
@skamphuis
@Timo-Breumelhof commented on Fri Mar 01 2019
workaround:
UPDATE TABS SET SiteMapPriority = 0.5 WHERE TABID IN (SELECT TabID
FROM Tabs
WHERE (PortalID = 0) AND (SiteMapPriority = 0) and (IsSystem = 0))
@schotman commented on Fri Mar 01 2019
Yes, it should
The text was updated successfully, but these errors were encountered: