OK, after looking everywhere, I managed to find a solution. Turns out things changes in 1.2 - the prototype directory is now not located on the web folder, but inside a plugin. That plugin needs to be activated on the command line by issuing the following command:
symfony plugin:publish-assets After doing that, symfony seems to set up special redirection rules for the plugins used on the proejct, like for example the / sfProtoculousPlugin directory that my templates kept trying to access. Then, bingo! Things work like magic :P So it seems all that is missing is to add that command to the Ajax Tutorial for 1.2.... Thanks for the help :) On Mar 21, 8:51 pm, Campezzi <[email protected]> wrote: > Hi again Lee, thanks for answering :) > > Indeed, installing v1.1 gave me the folder I was missing. Maybe there > is something wrong with the 1.2.4 package after all... I wonder how > that could be informed to the folks that take care of the project? > > Kind Regards, > Campezzi > > On Mar 21, 8:28 pm, Lee Bolding <[email protected]> wrote: > > > Hmm... you're missing a directory data/symfony/web/sf/prototype, which > > contains : > > > css/input_auto_complete_tag.css > > and > > js/builder.js > > js/dragdrop.js > > js/index.html > > js/scriptaculous.js > > js/sound.js > > js/controls.js > > js/effects.js > > js/prototype.js > > js/slider.js > > js/unittest.js > > > I wouldn't be surprised if you've also got other files missing... > > > I guess it could be a bad path or directory separator in the PEAR > > package. > > > I'm out of ideas, other than suggesting you try installing 1.1 and see > > if that works - if it does, it eliminates your platform and points the > > finger at the package you've been trying to install. > > > On 21 Mar 2009, at 23:07, Campezzi wrote: > > > > Hi Lee, > > > > Thanks for your answer. I checked my cli php.ini settings and they > > > seemed to be fine - just in case, I uninstalled symfony and installed > > > again, and still got the same issues (even though the installation > > > returns an OK message). I'm going to try VirtualBox, but I don't think > > > it will work - I downloaded the symfony source from symfony- > > > project.org and, browsing the files, I see that the file structure > > > there looks just like my installation does. > > > > Any other ideas? > > > > Thanks again, > > > > Campezzi > > > > On Mar 21, 7:30 pm, Lee Bolding <[email protected]> wrote: > > >> Possibly your the php.ini for cli didn't have high enough > > >> memory_limit. This makes the PEAR installer bail halfway through > > >> installation - I guess those are the kind of symptoms you'd get, > > >> missing file cos they weren't copied before the installation bailed. > > > >> Try uninstalling (via PEAR), changing your cli memory_limit to 128M > > >> and then reinstalling via PEAR. > > > >> Windows is a bitch to develop on. I'd recommend you build yourself a > > >> Linux VM with VirtualBox (it's free) and save yourself a world of > > >> pain :) > > > >> On 21 Mar 2009, at 20:59, Campezzi wrote: > > > >>> Hi there, > > > >>> I recently installed symfony on my test server at home (Windows box > > >>> running WAMP) using PEAR. The installation went well, and everything > > >>> seemed to be working. However, when I tried running the Ajax > > >>> tutorial, > > >>> I noticed it wasn't working for a simple reason - the necessary > > >>> libraries were not being included. > > > >>> At first I thought it was a simple httpd.conf problem, but when I > > >>> checked my data folder, I noticed there were no JS files there. > > >>> All I > > >>> have is: > > > >>> data/symfony/web/sf/calendar > > >>> data/symfony/web/sf/sf_admin > > >>> data/symfony/web/sf/sf_default > > >>> data/symfony/web/sf/sf_web_debug > > > >>> I could download script.aculo.us (which comes with prototype > > >>> bundled), > > >>> but I don't know where exactly the JS files should go. > > > >>> So my question is twofold: > > > >>> 1. why would the PEAR installation not install the JS libraries on > > >>> the > > >>> data folder by default? that's odd. > > >>> 2. if the solution is to actually download the libraries, where > > >>> should > > >>> I drop them exactly in my symfony data folder? I know I'll use > > >>> them in > > >>> other projects, so it would be better to have a "permanent" solution > > >>> on this one... > > > >>> Thanks for your time and patience! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
