EDIT: The entire answer updated, to accommodate new cms page creation.
Ok, you can solve this in multiple ways, rewrites are one (rewriting controller and models of the cms system (yuk)) or just using observers/events. I prefer observer events, as it makes for higher compatibility with other 3rd party modules.
As per my previous answer, the flaw was that I suggested using only the 'cms_page_prepare_save' event, but as you had found that does not work for new pages. Why? Because the page model has not saved yet, thus no page id.
However, this event is the only event available that also passes the request data, so it must be used.
The solution: Use two events. The first stays as 'cms_page_prepare_save', which allows you to get the request data, and the second will be an event on the model save after 'cms_page_save_after'.
Thus the process will be:
- Observe the 'cms_page_prepare_save' event
- Grab the request data and extract your tabs data.
- Set that against the page model that was also passed (this is temp storage so you can use it later)
- Listen to the cms page model save after event. 'cms_page_save_after'
- Grab your data out of the page model, as well as the page id and use it.
So here goes:
In the observer event 'cms_page_prepare_save' you will have code like this:
public function cms_page_prepare_save(Varien_Event_Observer $observer) {
$requestParams = $observer->getRequest()->getParams();
$page = $observer->getPage();
$page->setData('request_params',$requestParams); // save the request data to the page model. This will not intevere with normal model functionality as it will be ignored by anything else.
return $this;
}
Next you have another observer on 'cms_page_prepare_save' event with this code:
public function cms_page_save_after(Varien_Event_Observer $observer) {
$page = $observer->getObject();
$requestParams = $page->getRequestParams();
// do what you need to do with your tab data, which is now in $requestParams
return $this;
}
Ideally in the cms_page_prepare_save observer code you'd only store your tabs information, not the entire request params, as that could be a lot of data.
You could also use this event to filter/sanetise/check your data, before the models get saved.
Hope this adjusted answer helps.
the fieldsets are only a way to organize the fields visually. Thy shouldn't have an impact in saving the data from them. There shouldn't be any difference if the fields are all in one fieldset or in 10. There is something else that's preventing the fields from being saved.
If you added the table columns corresponding to the second fieldset by altering the table, you should clear the cache. Even if the cache is disabled ZF still caches the table schema.
Also make sure that the field names are the same as the column columns.
If the fields in the second fieldset are date fields maybe there is a problem with the date format you are using.
Add this in the controller on the save action
Zend_Debug::dump($this->getRequest()->getPost())
and see how the values are sent to the controller.
Best Answer
The problem is, you need to transform your array to a string before saving it to the database.
This can be done in an observer listening to
cms_page_load_after/beforeto transform string to array andcms_page_save_before/afterto transform it back. And after the saving it should be transformed back...How to use event/observer: http://www.magentocommerce.com/wiki/5_-_modules_and_development/0_-_module_development_in_magento/customizing_magento_using_event-observer_method in the observer you get the
$page = $observer->getPage()and then you set$page->setYourAttribute(implode(',', $page->getYourAttribute());