[symfony-users] No executed php code in component

[Benoit Pr]

Hi,

I am facing a problem which is taotally driving me nuts!

I have some php code in a component (normal, you'll say), and I am
using values in php to inject them into some javascript.

But, each of this values is not correctly interpreted...

Example: I have a value defined in app.yml, I call it with
sfConfig::get('app_myvar') and null is returned.

Same thing with url_for: "echo url_for('@login');" to have the routing
link of a login page. With url_for on this page, this is worst, the
all page turns blank.

In dev environement everything is working fine. In prod environment
nothing of written above is working.

I am under Symfony 1.4

Benoit

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en

[symfony-users] Re: Symfony 1.4-compatible minifier for Symfony now included in Apostrophe, can be used in any Symfony project

[Benoit Pr]

Hi,

I just implemented this plugin, which seems very interesting (1.4
compatible also).

However, when i use a_include*, I am collecting js and css which are
not in my project, like these one for example:
/apostrophePlugin/css/a-reset.css
/apostrophePlugin/css/a-utility.css
/apostrophePlugin/css/a-forms.css
/apostrophePlugin/css/a-buttons.css
/apostrophePlugin/css/a-navigation.css
/apostrophePlugin/css/a-components.css
/apostrophePlugin/css/a-area-slots.css
/apostrophePlugin/css/a-engines.css
/apostrophePlugin/css/a-admin.css
/apostrophePlugin/css/a-colors.css
/apostrophePlugin/js/aUI.js
/apostrophePlugin/js/aControls.js
/apostrophePlugin/js/plugins/jquery.autogrow.js
/apostrophePlugin/js/plugins/jquery.keycodes-0.2.js
/apostrophePlugin/js/plugins/jquery.timer-1.2.js
/apostrophePlugin/js/a.js

How do disable the call to thoses files?

Thanks by advance,

On 18 août, 16:34, Stéphane  wrote:
> Done :http://trac.apostrophenow.org/ticket/533
>
> Cheers,
>
> Before Printing, Think about Your Environmental Responsibility!
> Avant d'Imprimer, Pensez à Votre Responsabilitée Environnementale!
>
>
>
> On Wed, Aug 18, 2010 at 3:24 PM, Tom Boutell  wrote:
> > A specific task would be convenient for those who consider 'symfony
> > cc' too heavy, and I could still invoke it automatically from a
> > 'symfony cc' hook. Would you mind opening a ticket on
> > trac.apostrophenow.org to remind me to look at this?
>
> > On Aug 17, 9:54 am, Stéphane  wrote:
> > > +1 for the specific task !
>
> > > Before Printing, Think about Your Environmental Responsibility!
> > > Avant d'Imprimer, Pensez à Votre Responsabilitée Environnementale!
>
> > > On Tue, Aug 17, 2010 at 3:52 PM, Daniel Lohse
> > > wrote:
>
> > > > Mhm, I somehow I knew that this would have been t easy. (:
>
> > > > But okay, so we do need to cache these relations array(bundle =>
> > > > sha1sum.ccsgz) somewhere it gets loaded on every request and I'd guess
> > the
> > > > app.yml.php file is a good place. Still, using this approach does not
> > > > necessitate – or even need for that matter – manual cache invalidation
> > > > because we could send the far future Expires header everytime. If files
> > in
> > > > that bundle change, clear the files (not necessarily with a brute-force
> > > > symfony cc) and they are rebuilt on the next page refresh. Maybe we
> > could
> > > > provide a apostrophe:clear-minified-resources [--js] [--css] [--all]
> > > > [--env="dev|prod|staging"] task so as to not need the brute-force
> > symfony cc
> > > > or go hunting for these minified files manually?
>
> > > > Cheers, Daniel
>
> > > > On 17.08.2010, at 15:32, Tom Boutell wrote:
>
> > > > > Daniel, this almost works and I got pretty excited thinking about
> > > > > it... but there's a tragic flaw.
>
> > > > > On the first page access you slurp up all the CSS files, minify them,
> > > > > md5 that and create a cache file. Fine.
>
> > > > > On the second page access you... can't point to the cache file
> > without
> > > > > first doing all of that again (everything except actually writing the
> > > > > file) just to figure out what the filename is. (:
>
> > > > > Opening all of the files, slurping them in and md5'ing them on every
> > > > > page access is overhead we do not want. So it makes more sense to
> > have
> > > > > a cache key.
>
> > > > > On Aug 16, 9:13 am, Daniel Lohse 
> > wrote:
> > > > >> Sorry for being a bit slow today: why would we need cache
> > invalidation?
> > > > If the filename of the compacted file(s) is a hash generated from the
> > > > contents of the file then after one file changes and the
> > scripts/stylesheets
> > > > are re-generated the filename changes. The browser then should just
> > request
> > > > the file because it doesn't about that file yet (filename is not the
> > same).
>
> > > > >> Am I missing something here?
>
> > > > >> Cheers, Daniel
>
> > > > >> Sent from my iPad
>
> > > > >> On Aug 16, 2010, at 2:59 PM, Tom Boutell  wrote:
>
> > > > >>> You're right, we do need cache invalidation. I just came up with a
> > > > >>> clean way to do it without tweaking app.yml settings, adding a
> > table
> > > > >>> or making glob() calls: just use a file in the asset-cache folder
> > to
> > > > >>> hold the current cache key. The OS should cache reads from that
> > file
> > > > >>> extremely well.
>
> > > > >>> It may even be possible to avoid the filesystem hit by writing it
> > as a
> > > > >>> PHP file in cache/frontend/prod/config that just calls
> > > > >>> sfConfig::set(). Then with any luck it would be autoloaded and even
> > > > >>> cached by APC until its modification date changes just like an
> > app.yml
> > > > >>> setting would. But plain old file_get_contents() calls to a simple
> > > > >>> file with an asset cache version number in it would also get cached
> > > > >>> nicely by the operating system so it might be overkill to try to
> > wedge
> > > > >>> it into Symfony's cache.
>
> > > > >>> O

[symfony-users] htaccess & 2 applications in /web: strange problem

[Benoit Pr]

Hi,

I have 2 applications: app1 & app2, which directory web files are both
in /web.

Here's my problem:while rewrite works perfectly for app1, rewrite
works partially for app2: css, img & js are not loaded.

When we both exchange app* places in .htaccess, app2 works perfectly,
then app1 works partially: no load of css img & js.

Here's my .htaccess, did I forgot something? I am on this since 2
days... :(

Cheers

Options +FollowSymLinks +ExecCGI
ExpiresActive On

# 1 month

#  Header set Cache-Control "max-age=2592000, public"
  ExpiresDefault "access plus 1 month"


# 1 month

  Header set Cache-Control "max-age=2592000, proxy-revalidate"


# 2 month favicon

  Header set Cache-Control "max-age=2592000, proxy-revalidate"


# 1 MIN

 Header set Cache-Control "max-age=60, private, proxy-revalidate"



  RewriteEngine On

  # uncomment the following line, if you are having trouble
  # getting no_script_name to work
  RewriteBase /

  # we skip all files with .something
  #RewriteCond %{REQUEST_URI} \..+$
  #RewriteCond %{REQUEST_URI} !\.html$
  #RewriteRule .* - [L]

  # we check if the .html version is here (caching)
  RewriteRule ^$ index.html [QSA]
  RewriteRule ^([^.]+)$ $1.html [QSA]
  RewriteCond %{REQUEST_FILENAME} !-f

  # no, so we redirect to our front web controller
  RewriteCond %{HTTP_HOST} ^hostapp1 [NC]
  RewriteRule ^(.*)$ index.php [QSA,L]

  RewriteCond %{HTTP_HOST} ^hostapp2 [NC]
  RewriteRule ^(.*)$ frontend.php [QSA,L]



-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en