This project is read-only.
1

Closed

Inconsistencies when creating new pages

description

Problem #1:
Go to Admin > Pages and click 'Add New Page'. In 'Insert Page' field you get correctly 'After' for radios, but for ComboBox instead of having selected first page in root you always have selected 'Pages' which is second nested page of 'Admin'.
 
Problem #2:
Go to Admin > Pages and select any nested page in ListBox and click 'Add New Page' you will get it inside 'Insert Page' correctly. However Parent Page will default to <None Specified> instead of correct parent page. Same problem is when you go to nested page and click on 'New' in Common Tasks > Actions on Ribbon ControlPanel ..
 
Its somewhere inside ManageTabs.ascx.cs ... I had not much time to look for it, but its surely something simple.
Closed Jun 14, 2010 at 6:23 AM by zyhfish
same with the vb's version.

comments

zyhfish wrote Jun 12, 2010 at 2:55 AM

i can not reproduce the situation, maybe i have lost some action, can you write more detail step by step?

Xeevis wrote Jun 13, 2010 at 10:38 PM

Took me a while to determine cause why im getting Problem #1 ... This happens if you remove home page from Site Settings (I did that because i load homepage dynamicaly based on user locale). Now i know this I can set homepage for each locale instead of just redirecting to them.

Problem #2 Is more serious which I get under all cirmustances. For example if you create page structure Home > "Some Sub Page" then go to Admin > Pages and select "Some Sub Page" in listbox then you click on plus (Add New Page) you will have selected in Insert page field values "After" and in combobox "Some Sub Page" ... problem is this choice has no impact since Parent Page is set to <None Specified>. I don't know how it works in VB.NET version, but you either have <None Specified> and you can select Before-After-Add to End in root. Or you will have Parent set to parent of page you selected in listbox. Hope i made myself clear :).

zyhfish wrote Jun 14, 2010 at 6:21 AM

i have test it in vb's version, they have the same process, so i think we don't need to change this in c#'s version. i will close this work item, thank you.

wrote Jun 14, 2010 at 6:22 AM

zyhfish wrote Jun 14, 2010 at 6:22 AM

same with the vb's version.



** Closed by zyhfish 2010/6/13 22:22

zyhfish wrote Jun 14, 2010 at 6:22 AM

same with the vb's version.

wrote Jun 14, 2010 at 6:23 AM

wrote Feb 13, 2013 at 11:46 PM

wrote May 16, 2013 at 4:13 AM