Thanks for testing this.
In brief:
This is a normal behaviour.
You simply cannot use "Redirect Page" as block name since this is a reserved basic property of the content type.
I'll try to explain the details:
Each block will become a property of the content.
Therefore each block needs an 'id'.
This id must be unique.
The id will be the name of the block but without whitespaces and lower case.
That means ' block="Redirect page" ' wil have the id 'redirect_page'.
This id will be the index of the $params array (what just contains the $_POST data when submitting the edit content form) and the name of the property stored in the database.
And that is why you cannot use "Redirect page" as block name since in the code there already is a property called 'redirect_page'.
(It is for FrontendUsers page access. You won't see it if you haven't installed FrontendUsers.)
By the way (is this bug report worthy?):
Just try to use a block called title and edit a page of content type content (the default one).
The page title will be shown as value of that content block since the default content type does not check if the name of the block (wich will become the name of a content property) already exists or is a basic property. So when getting the value of the content block the content type will get the property named "title". Wich is actually the page title but not the additional content block.
And now just imagine what happens if you save the changes.
Right.
If you change the content of that block you will change the page title.
Even if you never wanted to do that.
(Imagine what happens if you have a block called "alias", "menutext" etc. ... :o )
So actually no additional content block will be added in this case but just the page title will be overwritten.
That means in the default content type you can overwrite the basic content properties by the content blocks. What in my opinion is bug and should be fixed.
Also if you use block names several times you override the previous one.
The default content type does only show one content block (the last one) while the user might wonder where the f*ck the other content blocks are.
(I was almost getting crazy about that until i realised that there was a fault in my template ::) )
That is why i check if the content blocks name is reserved by any basic content property.
The same thing happens if you use a block name twice.
In the extensible contenttype at this place where the content block would be shown it will print out a notice that this block name is ambigous, block names must be unique and that this block will be ignored (so you cannot overwrite basic properties or previous content blocks).
In opposite to the default content type i only process the first found content block and all following ones with the same name will be ignored but replaced by at least a tiny notice.
(Just to prevent other users to run into the same crazyness i did
)
Back to topic... So if you have this message just check your page template for this param that has the value "Redirect page" and change this value e.g. to "My Redirect Page".
If you don't like to have "My Redirect Page" as the prompt of this block just use the param label to assign a custom prompt to this block instead of the block name:
{content block="my redirect page" label="Redirect Page" block_tab='Access' type="text" oneline=true assign='redirect_page'}
or
{XContent block="my redirect page" label="Redirect Page" block_tab='Access' type="text" oneline=true assign='redirect_page'}
Notice:
In the next version of this content type module the module/plugin name will change to "AdvancedContent" since "XContent" is a registered trademark and anyway the module has nothing to do with the CMS XContent.
