Frog CMS

Hi, See the Page model (in /frog/app/backend/models/Page.php) and how the PageController (/frog/app/backend/controllers/PageController.php) use it (particulary the _add method if you want to create a new page).

I'm not sure it is wise to use Frog internal code to do that. Any method you see which is prefixed with an underscore (_) should be considered off-limits since it is a private method and might change in future Frog versions.

If you explain why you're trying to add a page programmatically, we might be able to point you in the correct direction or simply add a method to the Plugin API to provide the functionality you need.

So you have a page with dynamic content which changes daily (couple of rss feed for example), and each day you want to save that day's content so people can refer to it later for example....

My guess is you could go one of three ways with this:

1. You could dynamically create a page in Frog. This method would have a couple of side effects: the pages tab would quickly fill up with your archive pages / content editors might lose track of the overview
2. You could use a custom database table for your plugin and store the archived content in there. Then your plugin could provide multiple methods of accessing that content and dynamically create the archived page when a user wants it.
3. You could store archived data on disk somewhere and dynamically access it to create an archive page when people need it.

Option 1 would require the least amount of work I guess since it would probably be a "simple" copy-paste of content kind of action. Downside would be the number of pages it creates and a possible lack in overview for content editors.

Option 2 is more similar to the current "Archive" plugin's behaviour and thus more in line with Frog's "style" if we have any. ;-) Anyway, this would also give you the most flexibility with regards to accessing the data in custom ways. Here the downside is that it would require more work to do properly and the database might grow very quickly in size.

Option 3 is the least desirable in my humble opinion since it would require having disk access, would require you to write and read files to disk, have the appropriate permissions, etc. etc.

My advice? Use option 2....

If you really don't want to do that, I guess we can put a createPage method (and related methods) in the Plugin API. I think that probably wouldn't be a bad idea anyway. I'll discuss that with the guys to see if they like it.

@ricks - deep in the recesses of my "mind" there was a memory that this came up once before. I managed to find this thread on "paging in the admin". I think that's the only place it has come up before. Something worth thinking about?

Nope… there wasn’t an issue/feature request recorded for this in the issue tracking system so I kind of forgot about this. (hint.. hint..)

;-)