I have a problem here. My Zend_Forms do not render in view script.
Via FirePHP i have spotted a lot of "Need PHP 5.3 to get value"
Could someone confirm?
What should i do if i have PHP 5.2.11?
Thanks!
Yes. They are compatible. I am not aware of any features that would require 5.3.
Install XDebug or Zend Debugger to see what's wrong.
They weren't supposed to be using anything that would require PHP 5.3 until ZF2.0 (which, if you read the blogs, is due soon). Did you download the framework manually, or are you tracking it via an svn:external? If you are, you may want to do it differently as from here on in we're likely to see new code requiring 5.3 being checked in.
Related
I want to create a php application that can be used by many users, As laravel 4 requries 5.3.7 i am confused weather to use it or not because many of the users may not have the php version supported as they will be using shared hosting.
How to overcome this ? Is it by using older version of laravel or some other solution please help me. I am really intersted in using laravel cause of its robust nature.
To be honest, depending on what your application is, it's probably enough to think that most users are either already going to be on PHP 5.3.7+ or they will be willing to upgrade to the latest version or a more recent version of PHP.
When PHP 5.3.20 was released, there was an extremely public announcement that PHP 5.3 was going to be EOL'd after March 2013.
It's now obviously past March 2013.
People should have moved to PHP 5.4 by now. If your application is a one of a kind, or the best in it's class, then you should not need to worry about what version of PHP is being operated on, as people should either
be running PHP version > 5.3.20
be able to upgrade to a PHP version > 5.3.20
The Laravel dependancy on PHP 5.3 is a nice one, and to be honest, with all of the new features and general code style of Laravel being introduced, I would not be surprised if the version requirement is increased to PHP 5.4 "soon" (in say the next 6-12 months).
If you want to create an application used by many users, simply advise them that there is a minimum requirement for PHP 5.3.7. This is not too unusual for web applications.
For example, a very popular PHP forum phpBB has required PHP 5.3.3 since March 2012.
I've been asked to make some changes to a site that was built with Expression Engine 1.6.8. Even though I'm not familiar with this CMS, I can find my way around to make the updates, except I'm not sure about adding a contact form. I'm guessing that ultimately I'll have to upgrade this version to the newest (2.7, I believe?) in order to get the tags found on this page to work: http://ellislab.com/expressionengine/user-guide/modules/email/contact_form.html?
My only hesitation in making the upgrade is my unfamiliarity with EE, and the fact that someone else is probably creating a brand new website for the one I'm working on, and very likely without EE (so I'm learning something that I may not need again).
Any suggestions for a quick fix, or should I just bite the bullet, upgrade, and use what I've found?
Take a look at the EE 1.x docs.
At a glance it appears that syntax has changed little bit. Maybe that's why your EE2 tags were not working in EE1.
I would definitely try to use the tags as shown in the EE1 docs if this site is that old. Making a jump from 1.6.8 to 2.7 can become treacherous due to variables such as how the templates were coded, which add-ons were used, if those add-ons are even available any longer, what functionality was deprecated or absorbed, etc...
I only say ditch the efforts because you mentioned having another site in progress. If you would like to work through the updates/upgrades, follow the docs here and here and learn it. It is definitely worth the learn. Once you tap into EE, it's hard to roll back.
I ended up writing my own html code within the template and processed it with a php script to send the form input to an email address, just as I normally would on a website. Not being familiar with ExpressionEngine, I don't think I understood why I was continually being referenced to use a module in order to do this, but I suppose for anyone who is not a coder but is experienced with EE, that would be the way to go. From what I understand, the email module is not free and does not come with the core version, which is what I had to work with, but comes with the licensed version, which made this all the more confusing.
my Joomla-backend ist destroyed. i can do a log in in a normal way, but then i see only text, no graphics. and also the wohle site is not visible and i can't scoll it. i made a screenshot, please look at it to see what i mean. i have to upgrade my Joomla Version but i cant do it with this broken backend. The current Joomla Version is 1.5.26
So, how can i fix this? I need full acces to my backend. Please help.
This is why we should not use older version of joomla.
you must install newer version of joomla
It is more reliable and secure.
Here is the step by step migration process
I've just started getting into Catalyst, and I've been finding it really helpful. One of my favorite things about it was TTSite in that it got me going fast and gave me something to develop with without just black text (and it required no work from me to setup). However, I've been reading in a lot of places that it's buggy, or even deprecated as mentioned here on the actual Catalyst tutorial. However I've found it nothing but helpful and have had no issues, so basically I'm wondering is there reason for me to be worried and not use it? And if so, does anyone know of a similar alternative that kind of gives you a base template set up to work within? Thanks a lot!
I don't think TTSite is officially deprecated in terms of support .. it is still included in the Catalyst::View::TT distribution as of 0.39 (released 10-April 2012). I suspect it is more a case of some developers disliking the base templates that are provided and TTSite no longer being recommended as part of the default Catalyst tutorial.
TTSite provides a very simple base that has some quirks. For example, the context object is called Catalyst instead of c, and the use of TT's WRAPPER command can get in the way of AJAX and non-html views.
More background reading:
Discussion on the Catalyst-Dev mailing list regarding changing the Catalyst tutorial from TTSite to straight TT
Catalyst wiki: disabling TT wrapper for AJAX requests
A blog post on TTSite including changing Catalyst context reference to c
A modern base theme would probably start with something like Bootstrap or one of the 960 Grid HTML/CSS frameworks. I'm not aware of an actively maintained Catalyst::View helper that would be a better replacement for TTSite, but also don't find it too onerous to drop in the latest version of Bootstrap :)
Is there an extension that would check whether there are newer versions available to the installed extensions on a Joomla site, and would notify the site administrator?
Ideally, I am looking for something similar to Drupal's "Update" module.
I understand that there is no central place for keeping all these modules and their versions for Joomla, but at least a lot of them are available on the Joomla Extensions site, along with the needed information, so perhaps somebody wrote a tool that checks that source?
Aha, looks like this is to be included in Joomla 1.6, according to this description (check out the "Find Updates" button, looks great).
But if you are using Joomla 1.5 until 1.6 is stable check out: http://extensions.joomla.org/extensions/core-enhancements/installers/9332
Excellent for keeping components up to date :)