Don't assign an url to the page, then it will be ok. The page will be rendered
inside a tag but nevertheless it's the easiest method to accomplish
almost the same markup.
Regards, Jurian
--
Jurian Sluiman
CTO Soflomo V.O.F.
http://soflomo.com
On Thursday 01 Jul 2010 06:37:21 Mike A wrote:
> K
Hi,
I have a module called let's say products. In every view file of module
products I need some common variables. Thus I want to avoid having the same
code over and over in every action of products module to set those
variables.
So I made a Plugin and in its preDispatch function I check if a re
Putting them in the init function of the controller should work? Am I wrong?
On Thu, Jul 1, 2010 at 11:07 AM, debussy007 wrote:
> Hi, I have a module called let's say *products*. In every view file of
> module *products* I need some common variables. Thus I want to avoid
> having the same code o
Init works best for this kind of thing.
class Products_YourController extends Zend_Controller_Action
{
public function init()
{
$this->view->yourVariable = 'The answer is 42';
}
}
That is assuming you only need it in that one controller, but all actions of it.
If you want the
Thank you,
If I'm not wrong I could use the preDispatch() function as well.
Seems that I can set variables to the view successfully.
--
View this message in context:
http://zend-framework-community.634137.n4.nabble.com/Set-variables-for-the-view-at-every-request-to-a-specific-module-tp2274762p2
Yes you could, but there is a difference. The best explenation is in
the manual, quoted here for your convinience:
Note: Usage of init() vs. preDispatch()
In the previous section, we introduced the init() method, and in this
section, the preDispatch() method. What is the difference between
them, a
-- debussy007 wrote
(on Thursday, 01 July 2010, 01:07 AM -0700):
> Hi, I have a module called let's say products. In every view file of module
> products I need some common variables. Thus I want to avoid having the same
> code over and over in every action of products module to set those variable
On Wed, Jun 30, 2010 at 4:46 PM, Bill Karwin wrote:
> Common wisdom says that one join is always better than three or six, but
> this actually performs much *worse* (if you use MySQL), because virtually
> any query using GROUP BY uses a temporary table, which kills performance
> because disk I/O i
Hi Andrew,
Just jumping in, here is another approach:
SELECT P.product_id, P.product_name, P.price
FROM
products AS P
INNER JOIN product_tags AS PT
ON P.product_id = PT.product_id
INNER JOIN tags AS T
ON T.tag_id = PT.tag_id AND T.tag IN
On Thu, Jul 1, 2010 at 11:55 AM, Vincent de Lau wrote:
> Hi Andrew,
>
> Just jumping in, here is another approach:
>
> SELECT P.product_id, P.product_name, P.price
> FROM
> products AS P
> INNER JOIN product_tags AS PT
> ON P.product_id = PT.product_id
> INNER J
I have a problem that I cannot seem to wrap my head around.
3 text fields on my form are "start dates", and another 3 text fields are
"end dates". I need to validate the end dates to their corresponding
starting dates to ensure they are later than the start dates.
I created a custom validator f
Would be the benefit or disadvantage of using an action controller
instead? Is it only that the action controller plugin might be called
multiple times?
On 7/1/2010 8:58 AM, Matthew Weier O'Phinney wrote:
-- debussy007 wrote
(on Thursday, 01 July 2010, 01:07 AM -0700):
Hi, I have a modu
Try this tutorial to start: http://akrabat.com/zend-framework-tutorial/
--
View this message in context:
http://zend-framework-community.634137.n4.nabble.com/Request-about-zend-framework-tp2272686p2275687.html
Sent from the Zend Framework mailing list archive at Nabble.com.
13 matches
Mail list logo
