vb wrote:
Do you have resources.frontcontroller.params.prefixDefaultModule = true
in your ini file?
And in _initAutoload, the namespace parameter should be Pagina, no?
Hi, Thanks for your answer. Yeah, I discovered this option while my message
was pending so long. Pfew.
But it works
First of, you might consider this question also helpful:
http://stackoverflow.com/questions/1579638/what-is-the-best-way-to-represent-recurring-events-in-database
Brenton Alker-3 wrote:
If the timespans are really complex, in essence: can not be catched in a
limited amount of time values,
Brenton Alker-3 wrote:
solve.
1. How would I persist this information?
The start date is easy, it's just a date.
The interval I'm not sure about. A number of seconds (or days if it's
only accurate to date) could work for basic things like every week. But
what about irregular things
tfk wrote:
Maybe you could file a feature request. I'd def. vote for it. E.g. a
lot of components support a fluent interface and this one def. breaks
the pattern. Or maybe the author can comment what they had in mind
when they implemented it.
Here you go:
tfk wrote:
But also those mean BC breaks.
True, but I think this can nonetheless be done in 2.0
--
View this message in context:
http://www.nabble.com/Why-does-Zend_URI%3A%3AsetQuery-return-old-query-string--tp25473629p25476445.html
Sent from the Zend Framework mailing list archive at
hey, count me in!
I would like to point out that that there is already a doctrine-firebug
plugin for zf: http://taat.pl/article/zend_framework_tutorial/step5/.
--
View this message in context:
http://www.nabble.com/RFC%3A-ZendX_Doctrine-tp23454552p25476504.html
Sent from the Zend Framework
