Skip to content
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 #2602

Closed
3 tasks done
schotman opened this issue Mar 1, 2019 · 6 comments
Closed
3 tasks done

Sitemap priority 0 when adding a single page #2602

schotman opened this issue Mar 1, 2019 · 6 comments

Comments

@schotman
Copy link
Contributor

schotman commented Mar 1, 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:

  1. Go to pages
  2. Click on add page
  3. add pagename and
  4. click the add page button

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

  • 9.2.2

Affected browser

not dependant of browser

  • Chrome
  • Firefox
@sleupold
Copy link
Contributor

sleupold commented Mar 1, 2019

IMO this should be fixed in DNN API code, not the database default value.

@Timo-Breumelhof
Copy link
Contributor

@skamphuis

@Timo-Breumelhof
Copy link
Contributor

workaround:

UPDATE TABS SET SiteMapPriority = 0.5 WHERE TABID IN (SELECT TabID
FROM Tabs
WHERE (PortalID = 0) AND (SiteMapPriority = 0) and (IsSystem = 0))

@schotman
Copy link
Contributor Author

schotman commented Mar 1, 2019

IMO this should be fixed in DNN API code, not the database default value.

Yes, it should

@valadas
Copy link
Contributor

valadas commented Mar 1, 2019

Issue moved to dnnsoftware/Dnn.AdminExperience #422 via ZenHub

@valadas
Copy link
Contributor

valadas commented Jul 29, 2019

By mistake this issue was copied instead of moved, closing it since this needs a fix in AdminExperience

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants