Re: [fw-general] Almost ready for 2.3.0!

[Artur Bodera]

Matt - I'm also wondering if we could tag ZFTool as 1.0 (ideally after we pull
in #66  which refactors
against ZendDiagnostics which is now at 1.0).

It would go nicely with 2.3 :-)


-- 
abod...@gmail.com
+48 695 600 936
http://thinkscape.pro


On Tue, Mar 11, 2014 at 7:54 AM, Artur Bodera  wrote:

> On Mon, Mar 10, 2014 at 9:24 PM, Matthew Weier O'Phinney  > wrote:
>>
>> Thanks in advance, and here's hoping to a smooth 2.3.0 rollout!
>>
>
> Two minor ones:
>
> I've found a possible regression in
> https://github.com/zendframework/zf2/pull/5720
>
> And found a bug in named value params in console routing, will send a PR
> today.
>
>
>
> --
> abod...@gmail.com
> +48 695 600 936
> http://thinkscape.pro
>
>
>

Re: [fw-general] Almost ready for 2.3.0!

[Artur Bodera]

On Mon, Mar 10, 2014 at 9:24 PM, Matthew Weier O'Phinney
wrote:
>
> Thanks in advance, and here's hoping to a smooth 2.3.0 rollout!
>

Two minor ones:

I've found a possible regression in
https://github.com/zendframework/zf2/pull/5720

And found a bug in named value params in console routing, will send a PR
today.



-- 
abod...@gmail.com
+48 695 600 936
http://thinkscape.pro

[fw-general] [ZF2] Abstract Factory Configuration Problem - Possible Infinite Loop Bug

[Jamie Krasnoo]

Hi All,

I'm just learning about ZF2 and need to make sure I'm using the service
manager abstract factory configuration in application.config.php correctly
before I start jumping up and down and pointing out a bug.

I'm using the Zend Skeletion Application as a base. In the
application.config.php file on the bottom is a config stub for the service
manager with the explanation that it will be the initial configuration to
seed the ServiceManager. I took this as a "place things here so you don't
have to repeat it in modules". Is this correct?

So what I did is move the base abstract factory configuration from
Application's module config over to application.config.php. As soon as this
was done and I tested it. I started getting out of memory errors from PHP.
I went in to php.ini and changed the memory from 128M to 256M and tested
again. It still used up the memory.

To try and trace the stack and see what's going on I installed xdebug and
set it up. I kept on running in to max nesting level errors. Hence the
thought that there is an infinite loop when abstract factories are placed
in application.config.php. Take it out and put that configuration back in
to module.config.php and the problem stops.

I attached my log configuration for your viewing pleasure just in case that
is the problem and I did something wrong there.

Jamie
<>

-- 
List: fw-general@lists.zend.com
Info: http://framework.zend.com/archives
Unsubscribe: fw-general-unsubscr...@lists.zend.com

[fw-general] Almost ready for 2.3.0!

[Matthew Weier O'Phinney]

Hey, everyone!

We're down to the last few pull requests and issues before we're ready
to tag 2.3.0. If you can, I'd really appreciate it if you'd test your
apps against the develop branch of ZF2 ("dev-develop" or "~2.3-dev" if
you use composer), and let us know ASAP if you see any show stoppers.

Thanks in advance, and here's hoping to a smooth 2.3.0 rollout!

-- 
Matthew Weier O'Phinney
Project Lead| matt...@zend.com
Zend Framework  | http://framework.zend.com/
PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc

-- 
List: fw-general@lists.zend.com
Info: http://framework.zend.com/archives
Unsubscribe: fw-general-unsubscr...@lists.zend.com

[fw-general] Re: Registering module event listeners early in the stack

[Marco Pivetta]

Hi Mark,

Attaching earlier than `onBootstrap` is only possible via `init`, and even
there, it would still be skipping some of the module loading related events.

What you can (eventually) do is something quite hacky, which is re-defining
the Application class so that it actually registers listeners during
`Application::init()`, and not during module loading.

I'd actually say that we can make that optional by allowing end users to
redefine their `index.php` (instead of using dirty hacks)

Cheers,


Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/


On 10 March 2014 18:42, moderndeveloper [via Zend Framework Community] <
ml-node+s634137n4661804...@n4.nabble.com> wrote:

> I'm working to get Zend Developer Tools to set a "universal" event
> listener for profiling of triggered events. I've gotten the code to 
> work,
> but with it being attached in the onBootstrap(), it's attached after
> several events have already fired. The listener is a
> SharedListenerAggregateInterface class that is being instantiated via the
> service manager based on a config option.
>
> Is there a way to actually get this attached earlier than onBootstrap? As
> far as I can tell, init() only has access to the ModuleEvent where I can
> get the event manager, but no the configs or service manager. Am I missing
> anything?
>
> --Mark G.
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://zend-framework-community.634137.n4.nabble.com/Registering-module-event-listeners-early-in-the-stack-tp4661804.html
>  To start a new topic under Zend Framework, email
> ml-node+s634137n634138...@n4.nabble.com
> To unsubscribe from Zend Framework Community, click 
> here
> .
> NAML
>




--
View this message in context: 
http://zend-framework-community.634137.n4.nabble.com/Registering-module-event-listeners-early-in-the-stack-tp4661804p4661805.html
Sent from the Zend Framework mailing list archive at Nabble.com.