Webinar – New in Zend Framework 1.10!
Jayson Minard (Editor-in-Chief) |
8 comments | March 11th, 2010
Zend Framework 1.10 sports a ton of new features, as well as completely revamped online documentation. In this webinar, Matthew Weier O’Phinney, Framework Project Lead, and Ralph Schindler, Zend Framework Software Engineer, will present a synopsis of the new features, discuss the new online documentation system and how it’s built, and answer your questions about the new release….
March 17, 2010 – 9:00 am PST – “More Information and Registration”:http://www.zend.com/en/company/news/event/webinar-new-in-zend-framework
8 comments to “Webinar – New in Zend Framework 1.10!”
March 11th, 2010 at 4:46 pm
The more information/registration link one zend.com takes you to a not found error page.
March 11th, 2010 at 5:05 pm
I tested the link again, the information page came up fine. I then selected to register and it asked me to login, then registered me for the event.
March 11th, 2010 at 5:12 pm
It seems to not like my email address and rejects it. I’m probably the only one experiencing it.
March 11th, 2010 at 5:14 pm
I am running into the same issue as bullring above. I get the first page, but when I click on the registration link and it kicks me out the Zend’s Webex, loads for a moment, and then kicks me back to Zend’s not found page.
March 15th, 2010 at 1:22 am
Same as woodsbw and bullring, I can login but then i get this:
Not Found
We’re sorry! The page you are looking for has been moved or does not exist. You may search for it here:
March 15th, 2010 at 5:57 pm
There is a nice example on why to use Zend Queue when you register for the webinar. It took around 5 seconds of waiting for the backend stuff to complete before I was directed to the ‘Thank you’ page.
Stick it in the queue guys!
March 15th, 2010 at 7:56 pm
It would be a good use for it, although I think the site hands off to Webex at that point and they do the transaction.
March 18th, 2010 at 9:54 am
Same here. I can login but after that, the page will not found. I hope this will be fixed soon…