[symfony-users] Re: bug caused by settings.yml
Have you change the value of max_forwards in the settings.yml ? It look like it is setup to 0. Thomas On Tue, Apr 29, 2008 at 6:21 AM, Charles Hilditch [EMAIL PROTECTED] wrote: I may have found a bug (in a recent 1.0.x version), should I post this here? (maybe the trac...) When the '.settings' key is uncommented and all sub-keys are commented I get the exception: [sfForwardException] Too many forwards have been detected for this request ( 0) ... I did this because I commented out the relative_root_url key under .settings then started getting this error. Took an hour to track this down. very frustrating. I'm using symfony v.1.0.11 (I know, should upgrade) So the tip is to never uncomment the '.settings' key unless you are going to use one of its sub-keys. ...may seem obvious but this will cause you a real headache if you didn't know about it. from settings.yml all: .settings: #available: on# Enable the whole application. Switch to off to redirect all requests to the unavailable module and action. # ... Anyone able to reproduce this error in 1.0.13+ or 1.1+? -- Charles Hilditch Web Developer Mob: 0415 166 137 [EMAIL PROTECTED] http://www.crh-systems.com/ -- Thomas Rabaix Internet Consultant --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: PDFs generation and Report Generator integration
On 28 Apr 2008, at 15:54, Nicolas Perriault wrote: On Mon, Apr 28, 2008 at 4:25 PM, Antonio [EMAIL PROTECTED] wrote: We use PDF generation for creating printing reports. If the user requests a report just after he or she changed the information, the report would have to be created on the fly. You can imagine to send a notification email when the PDF generation job is done, embedding a dowload link :) Yeah, I much prefer this approach rather than an AJAX page the user is stuck on whilst waiting for their report. That would result in a user being unproductive (and frustrated) for a significant amount of time whilst waiting for their report. If you put the job in a queue and allow the user to continue doing other tasks they'll be much happier :) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: PDFs generation and Report Generator integration
The Ajax options is only an alternative, you can combine : - a http meta refresh and/or an ajax - Email - Setting up a random yutube video while the user is waiting :) Depends on how long it take to generate the PDF. If it is only a few seconds, email is not the best solution... Thomas On Tue, Apr 29, 2008 at 10:42 AM, Lee Bolding [EMAIL PROTECTED] wrote: On 28 Apr 2008, at 15:54, Nicolas Perriault wrote: On Mon, Apr 28, 2008 at 4:25 PM, Antonio [EMAIL PROTECTED] wrote: We use PDF generation for creating printing reports. If the user requests a report just after he or she changed the information, the report would have to be created on the fly. You can imagine to send a notification email when the PDF generation job is done, embedding a dowload link :) Yeah, I much prefer this approach rather than an AJAX page the user is stuck on whilst waiting for their report. That would result in a user being unproductive (and frustrated) for a significant amount of time whilst waiting for their report. If you put the job in a queue and allow the user to continue doing other tasks they'll be much happier :) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: Symfony CMSes
Ok I've successfully managed to install sfDynamicCMS!
However all the generated urls seem to be in the form:
/page/show/url/about instead of just /about
I thought this was because of the symfony default rules I left in
routing.yml so I deleted them (as suggested by the instructions) but
then I get the error:
Unable to find a matching routing rule to generate url for params
array ( 'module' = 'page', 'action' = 'show', 'url' = 'about', ).
Any ideas?
On Mar 24, 2:55 pm, Eugene Leonovich [EMAIL PROTECTED] wrote:
sfDynamicCMS plugin looks interesting, but I have some difficulties
while installing them :(
When I tried to follow the link http://myproject/backend_dev.php/
sfDynamicCMSAdmin, I encountered an error:
Fatal error: Call to a member function getEditorCredentials() ...
To correct this error, I created an entry for a table
`sf_dynamic_cms_nav` manually:
INSERT INTO `sf_dynamic_cms_nav` (`name`, `application`, `culture`)
VALUES ('myapp', 'frontend', 'en');
Then, I tried to create a new navigation element in 'myapp' version,
but a new error was encountered:
Unable to execute INSERT statement. [wrapped: Could not execute update
[Native Error: Cannot add or update a child row: a foreign key
constraint fails (`fxc/sf_dynamic_cms_node`, CONSTRAINT
`sf_dynamic_cms_node_FK_1` FOREIGN KEY (`tree_parent`) REFERENCES
`sf_dynamic_cms_node` (`id`))] [User Info: INSERT INTO
sf_dynamic_cms_node
(TREE_LEFT,TREE_RIGHT,TREE_ID,CREATED_AT,UPDATED_AT) VALUES
(1,2,1,'2008-03-24 09:18:34','2008-03-24 09:18:34')]]
Could you help me to fix this errors?
Also, it would be good to attach some fixtures in a plugin.
My environment are:
PHP 5.2.3
mySQL 5.0.21
symfony 1.0.13-PRE
sfDynamicCMSPlugin-0.1.1
On Mar 21, 11:33 am, Sylvain - Com-Océan [EMAIL PROTECTED]
wrote: Hi I'm the developper of sfDynamicCMSAdmin
This project is in version 0.1.1 since some days, a lot of things still
have to be done... More over, it is more complex to use and to install
than others because it is not a turnkey solution, you have to extends
your module, design your menu (components) and templates.
On the other hand, I might permits more flexibility. CMS features are
basics at this time.
You can send me access = write me at [EMAIL PROTECTED]
--
Sylvain Papet - Développeur Web
Agence de communication Com-Océanwww.com-ocean.com/+33 4 90 66 48 82
Ian P. Christian a écrit :
cleve wrote:
Awesome idea Ian.
There's this one too:
http://trac.symfony-project.com/wiki/sfDynamicCMSPlugin
http://www4.pookey.co.uk/backend_dev.php/sfDynamicCMSAdmin
I've failed to get that one working. If the developer of this module
wants to contact me, I'll talk to them of give htem SSH access to the
site to setup a demo.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~--~~~~--~~--~--~---
[symfony-users] Disabling caching of config?
Hello In spite of having apps/admin/config/settings.yml set to dev: .settings: cache: off the configuration and some files created by the Admin Generator still end up in cache/ which is annoying as I often forget to clear it. Is there a way of comepletely disabling the cache? bye, -christian- --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] SO: Documentation about new Symfony 1.1 Features
Hi every: I'm preparing a Symfony mini conference to talk about new functionalities that come with Symfony 1.1. I found a lot of presentations but all them too abstract. I need some extended information, not manual or book, to understand the new features and then can explain to my students. Is just something like that: http://www.aide-de-camp.org/article/3/en/symfony-1-1-form-framework-and-the-mvc-pattern. ¿Any help? Cheers and thanks in advance Ing. Reynier Pérez Mira Grupo Soporte al Desarrollo - Dirección Técnica IP --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: SO: Documentation about new Symfony 1.1 Features
Hey, you might want to take a look at: http://www.symfony-project.org/blog/2008/03/25/symfony-1-1-beta-2-released-w hat-s-new a quite compact listing of all major changes from 1.0 to 1.1 Regards .:Fabian -Original Message- From: symfony-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Reynier Perez Mira Sent: Dienstag, 29. April 2008 14:55 To: symfony-users@googlegroups.com Subject: [symfony-users] SO: Documentation about new Symfony 1.1 Features Hi every: I'm preparing a Symfony mini conference to talk about new functionalities that come with Symfony 1.1. I found a lot of presentations but all them too abstract. I need some extended information, not manual or book, to understand the new features and then can explain to my students. Is just something like that: http://www.aide-de-camp.org/article/3/en/symfony-1-1-form-framework-and-the- mvc-pattern. ¿Any help? Cheers and thanks in advance Ing. Reynier Pérez Mira Grupo Soporte al Desarrollo - Dirección Técnica IP --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: SO: Documentation about new Symfony 1.1 Features
Fabian Lange wrote: Hey, you might want to take a look at: http://www.symfony-project.org/blog/2008/03/25/symfony-1-1-beta-2-released-w hat-s-new a quite compact listing of all major changes from 1.0 to 1.1 Of course, there's the UPGRADE doc too --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Cookie user session
I'm trying to keep users logged in for 2 weeks. I've changed the timeout setting to 2 weeks (sf_timeout: 1209600), but the symfony cookie expires at the end of the session. Any way I can fix that? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: Cookie user session
My understanding is that the user session will timeout either when a user closes his/her browser or when the time limit has expired. I think you want to create a separate cookie, i.e. not the session cookie. DC wrote: I'm trying to keep users logged in for 2 weeks. I've changed the timeout setting to 2 weeks (sf_timeout: 1209600), but the symfony cookie expires at the end of the session. Any way I can fix that? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: Cookie user session
Exactly. I was thinking maybe I can change that, so that user session will only expire on timeout, and not when users close their browser. The symfony cookie's default expire is set to zero. What I wanna know is, would changing that to 2 weeks work? And how would I go ahead and do that? On Apr 29, 6:05 pm, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: My understanding is that the user session will timeout either when a user closes his/her browser or when the time limit has expired. I think you want to create a separate cookie, i.e. not the session cookie. DC wrote: I'm trying to keep users logged in for 2 weeks. I've changed the timeout setting to 2 weeks (sf_timeout: 1209600), but the symfony cookie expires at the end of the session. Any way I can fix that? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: Cookie user session
I'm getting out of my depth here, but I think because symfony relies on the native php session that you can't maintain a session after someone has closed the browser. Anyone else? I think your best bet is to create a separate cookie when the user logs in and assign his user id to that cookie. Then each time a user visits the site, log them in automatically using the user id stored in the cookie. DC wrote: Exactly. I was thinking maybe I can change that, so that user session will only expire on timeout, and not when users close their browser. The symfony cookie's default expire is set to zero. What I wanna know is, would changing that to 2 weeks work? And how would I go ahead and do that? On Apr 29, 6:05 pm, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: My understanding is that the user session will timeout either when a user closes his/her browser or when the time limit has expired. I think you want to create a separate cookie, i.e. not the session cookie. DC wrote: I'm trying to keep users logged in for 2 weeks. I've changed the timeout setting to 2 weeks (sf_timeout: 1209600), but the symfony cookie expires at the end of the session. Any way I can fix that? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: Cookie user session
I`ll do that, manage my own cookie, but I'd suggest not just saving the userID, because such cookies are easy to toy with. In any case, thanks a lot for your time and insight! On Apr 29, 6:22 pm, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: I'm getting out of my depth here, but I think because symfony relies on the native php session that you can't maintain a session after someone has closed the browser. Anyone else? I think your best bet is to create a separate cookie when the user logs in and assign his user id to that cookie. Then each time a user visits the site, log them in automatically using the user id stored in the cookie. DC wrote: Exactly. I was thinking maybe I can change that, so that user session will only expire on timeout, and not when users close their browser. The symfony cookie's default expire is set to zero. What I wanna know is, would changing that to 2 weeks work? And how would I go ahead and do that? On Apr 29, 6:05 pm, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: My understanding is that the user session will timeout either when a user closes his/her browser or when the time limit has expired. I think you want to create a separate cookie, i.e. not the session cookie. DC wrote: I'm trying to keep users logged in for 2 weeks. I've changed the timeout setting to 2 weeks (sf_timeout: 1209600), but the symfony cookie expires at the end of the session. Any way I can fix that? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: Cookie user session
No problem. So what would you recommend storing in a cookie (I've never used them to be honest)? A random string maybe? unique to each user DC wrote: I`ll do that, manage my own cookie, but I'd suggest not just saving the userID, because such cookies are easy to toy with. In any case, thanks a lot for your time and insight! On Apr 29, 6:22 pm, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: I'm getting out of my depth here, but I think because symfony relies on the native php session that you can't maintain a session after someone has closed the browser. Anyone else? I think your best bet is to create a separate cookie when the user logs in and assign his user id to that cookie. Then each time a user visits the site, log them in automatically using the user id stored in the cookie. DC wrote: Exactly. I was thinking maybe I can change that, so that user session will only expire on timeout, and not when users close their browser. The symfony cookie's default expire is set to zero. What I wanna know is, would changing that to 2 weeks work? And how would I go ahead and do that? On Apr 29, 6:05 pm, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: My understanding is that the user session will timeout either when a user closes his/her browser or when the time limit has expired. I think you want to create a separate cookie, i.e. not the session cookie. DC wrote: I'm trying to keep users logged in for 2 weeks. I've changed the timeout setting to 2 weeks (sf_timeout: 1209600), but the symfony cookie expires at the end of the session. Any way I can fix that? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: Cookie user session
All, Symfony uses the php session handler to manage user state. You can change anything you need, by looking at the session factory. You can easily sign and encrypt your cookies and make them safe. Just override setCookie/getCookie. Cheers, Dustin On 4/29/08 8:30 AM, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: No problem. So what would you recommend storing in a cookie (I've never used them to be honest)? A random string maybe? unique to each user DC wrote: I`ll do that, manage my own cookie, but I'd suggest not just saving the userID, because such cookies are easy to toy with. In any case, thanks a lot for your time and insight! On Apr 29, 6:22 pm, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: I'm getting out of my depth here, but I think because symfony relies on the native php session that you can't maintain a session after someone has closed the browser. Anyone else? I think your best bet is to create a separate cookie when the user logs in and assign his user id to that cookie. Then each time a user visits the site, log them in automatically using the user id stored in the cookie. DC wrote: Exactly. I was thinking maybe I can change that, so that user session will only expire on timeout, and not when users close their browser. The symfony cookie's default expire is set to zero. What I wanna know is, would changing that to 2 weeks work? And how would I go ahead and do that? On Apr 29, 6:05 pm, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: My understanding is that the user session will timeout either when a user closes his/her browser or when the time limit has expired. I think you want to create a separate cookie, i.e. not the session cookie. DC wrote: I'm trying to keep users logged in for 2 weeks. I've changed the timeout setting to 2 weeks (sf_timeout: 1209600), but the symfony cookie expires at the end of the session. Any way I can fix that? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Linkin Park AOL Full Concert
[image: alt] http://www.kursatsenturk.com Linkin Park AOL Full Concert donwload now http://www.kursatsenturk.com sdc http://www.kursatsenturk.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Eurovision Song Contest 2008 donwload now
[image: Eurovision Song Contest 2008] http://www.kursatsenturk.com Download now Eurovision Song Contest 2008 http://www.kursatsenturk.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] The Summer of Trance vol.3
[image: alt] http://www.kursatsenturk.com download now http://www.kursatsenturk.com The Summer of Trance vol.3 http://www.kursatsenturk.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Advanced Batch Converter v4.0.18
[image: alt] Advanced Batch Converter v4.0.18 donwload nowhttp://www.kursatsenturk.com Bu program sayesinde tek tuşla çok kolay bir şekilde bir çok resim biçimini birbirine dönüştürebilirsiniz. Ayrıca resimlerin üzerlerinde yeniden ölçülendirme, kesme, çevirme ve ayna özellikleri gibi değişiklikler yapma imkanı da mevcut. Bir çok popüler resim biçimini destekler.http://www.kursatsenturk.com Does exactly what its title suggests, allowing you to easily convert multiple graphics files at the click of a button. More than that, you can also edit images directly in Advanced Batch Converter, to produce a variety of effects (resize, rotate, flip, mirror, crop, filters, watermarks, morphing effects, color enhancements etc). http://www.kursatsenturk.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Vista Service Pack 1
Vista Service Pack 1 http://kursatsenturk.com/vista-service-pack-1.htmNis 28, 2008 *sdc Tarafından | **Program*http://kursatsenturk.com/category/program * Kategorisine eklendi* [image: windows-logo]http://kursatsenturk.com/wp-content/uploads/2008/04/windows-logo.jpgVista SP1 çıktı çıkacak derken, sonunda indirilmeye sunuldu. 32bit, 64bit ve DVD ISO linkleri burada Service Pack 1′i indirmeden önce Vista'nızın 32 bit mi, 64 bit mi olduğunu kontrol edin, en düşük download boyutu 500 mb'ın üstünde.Eğer Windows Vista SP1 indirme boyutu size yüksek geliyorsa, Windows Update ile gelecek güncellemeyi bekleyebilirsiniz. Devamını oku »»http://kursatsenturk.com/vista-service-pack-1.htm#more-81 - 0 Yorum Yokhttp://kursatsenturk.com/vista-service-pack-1.htm#respond --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] FireFox’u Hızlandırı n
FireFox'u Hızlandırın http://kursatsenturk.com/firefox-hizlandirin.htmNis 28, 2008 *sdc Tarafından | **İnternet*http://kursatsenturk.com/category/internet * Kategorisine eklendi* [image: firefox]http://kursatsenturk.com/wp-content/uploads/2008/04/firefox.jpgFirefox zaten hızlı daha da hızlandırmak istiyorsanız aşağıdaki işlemleri yapabilirsiniz. Firefox tarayıcınızı açın… 1-Adres satırına about:config yazın ve enter deyin.. 2-Listeden aşağıdaki iki girişi bulun ve girişlerin üzerine sağ tıklayarak değeri değiştirerek true yapın…(her ikisin de de yapın)*network.http.pipelining - network.http.proxy.pipelining * Devamını oku »» http://kursatsenturk.com/firefox-hizlandirin.htm#more-83 --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Rapidshare de yenilikler var
Rapidshare de yenilikler varhttp://kursatsenturk.com/rapidshare-de-yenilikler-var.htmNis 28, 2008 *sdc Tarafından | **İnternet*http://kursatsenturk.com/category/internet * Kategorisine eklendi* Rapidshare de premium üye değilseniz ve daha önce dosya indirenlere yeni bir Ticket sistemi şu günlerde karşımıza çıkıyor. Rapid bu Ticket sistemini kedi ' li bir sisteme çevirdi .. 6 haneli rakam harf kombinasyonu içerisinde kedi resmi gizlenmiş olanları bulup bunları seçip kutuya girmeniz. köpek resimli olanları girerseniz yaklaşık 2 dakika zaman kaybetmiş olacaksınız . [image: rapidshare]http://kursatsenturk.com/wp-content/uploads/2008/04/rapidshare.jpg Bu arada bir kaç gün boyunca ticket sistemi yoktu Sistemde sorun yaşadılar sanırsam Devamını oku »»http://kursatsenturk.com/rapidshare-de-yenilikler-var.htm#more-86 --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Msn de kırmızı kalp devri
Msn de kırmızı kalp devrihttp://kursatsenturk.com/msn-de-kirmizi-kalp-devri.htmNis 29, 2008 *sdc Tarafından | **İnternet*http://kursatsenturk.com/category/internet * Kategorisine eklendi* http://kursatsenturk.com/wp-content/uploads/2008/04/msnkirmizikalp.jpg [image: msnkirmizikalp.jpg]http://kursatsenturk.com/wp-content/uploads/2008/04/msnkirmizikalp.jpgÇin'de yaşayan bir internet kullanıcısının tasarladığı sembol, 7 milyon MSN kullanıcısına ulaştı. Çin'in Beijing şehrinde yaşayan ve kendini kızgın gençlik olarak tanımlayan bir kişi 10 gün önce kırmızı bir kalp tasarladı ve bunu küçük bir web sitesine koyarak kendince ülkesine olan sevgisini göstermek istedi. Devamını oku »» http://kursatsenturk.com/msn-de-kirmizi-kalp-devri.htm#more-90 - 0 Yorum Yokhttp://kursatsenturk.com/msn-de-kirmizi-kalp-devri.htm#respond --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: Cookie user session
I assume by setting the timeout you are setting the value in settings.yml? This only impacts how symfony deals with the cookie presented by the browser -- not the lifetime of the cookie. To have the cookie preserved in the browser you need to modify the session storage parameters in factories.yml: http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Layer all: storage: class: sfSessionStorage param: session_name: my_cookie_name session_cookie_lifetime: 1209600 jbw On Tue, Apr 29, 2008 at 8:03 AM, DC [EMAIL PROTECTED] wrote: I'm trying to keep users logged in for 2 weeks. I've changed the timeout setting to 2 weeks (sf_timeout: 1209600), but the symfony cookie expires at the end of the session. Any way I can fix that? -- Joby Walker --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Standalone PHP script
I have a standalone PHP script, which basically looks like ?php echo Hello World!; ? for now :-), and I want to be able to run it from command line, not from the Web. No problem here. But I also have my Symfony Web application, and I want this command line standalone script to work with Symfony's Propel and generated models. How can I do that? Any examples? Thanks! --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: Standalone PHP script
http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Layer#Batch%20Files inrila wrote: I have a standalone PHP script, which basically looks like ?php echo Hello World!; ? for now :-), and I want to be able to run it from command line, not from the Web. No problem here. But I also have my Symfony Web application, and I want this command line standalone script to work with Symfony's Propel and generated models. How can I do that? Any examples? Thanks! --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: Standalone PHP script
On Apr 29, 2008, at 5:00 PM, inrila wrote: for now :-), and I want to be able to run it from command line, not from the Web. No problem here. But I also have my Symfony Web application, and I want this command line standalone script to work with Symfony's Propel and generated models. Batch files (and symfony init-batch): http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Layer#Batch%20Files To use Propel in a batch file, you'll need to initialize the database: preamble from above // initialize database manager $databaseManager = new sfDatabaseManager(); $databaseManager-initialize(); your code here How can I do that? Any examples? Thanks! -- Jacob Coby [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] [Slightly OT] Drupal
Hi, I have a client who wants a website. He is worried about having to overhaul the website at some point - perhaps with another developer - and so is quite keen to use a commonly used, open source product. I would prefer to use symfony, because I like it and it is infinitely (or almost) flexible. But I'm looking into other solutions, Drupal being one. So, having never used Drupal, would someone who has be able to compare it so symfony (yes, IO know that they're not the same beast)? I mean in terms of data model, forms, routing, etc. Thanks in advance. Tom P.S. I'm in no hurry to leave symfony by the way! --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: [Slightly OT] Drupal
Drupal is great for one thing, CMS websites. As soon as you go outside of that it becomes increasingly difficult and cumbersome to accomplish custom functionality. I am not arguing that the same end product cannot be accomplished, I am purely speaking from a point of view whether it makes sense or not. PHP covers a wide array of scale when it comes to web applications, which is why so many different tools exist. You have to ask yourself how much custom functionality you will need to build in addition to the native cms functionality you inherit from Drupal. If the answer is none, then I would recommend using Drupal, if the answer is yes then you'll have to gauge how much, how difficult and whether or not you can afford the cost of doing something custom in Drupal. If it is very custom, the cost could end up being greater than just doing it in symfony, and could be more expensive and difficult to maintain. - Jon On Tue, Apr 29, 2008 at 5:17 PM, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: Hi, I have a client who wants a website. He is worried about having to overhaul the website at some point - perhaps with another developer - and so is quite keen to use a commonly used, open source product. I would prefer to use symfony, because I like it and it is infinitely (or almost) flexible. But I'm looking into other solutions, Drupal being one. So, having never used Drupal, would someone who has be able to compare it so symfony (yes, IO know that they're not the same beast)? I mean in terms of data model, forms, routing, etc. Thanks in advance. Tom P.S. I'm in no hurry to leave symfony by the way! -- Jonathan Wage http://www.jwage.com http://www.centresource.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] sfDoctrinePlugin SVN organization changes
Hello all, I will be doing some work on the sfDoctrinePlugin for a new version. This will require that we make some changes to the way things are organized in svn. I am going to propose a structure for the branches and tags. Currently we have sfDoctrinePlugin/branches/0.1 and sfDoctrinePlugin/branches/1.0, below is an explanation of what each is currently, and what I want to change it to. sfDoctrinePlugin/branches/0.1 - The very first version of the sfDoctrinePlugin, which is linked to a super outdated version of Doctrine. This branch likely doesn't even work anymore. I would recommend removing it completely? sfDoctrinePlugin/branches/1.0 - The current stable sfDoctrinePlugin 1.0 that is compatible with symfony 1.0 sfDoctrinePlugin/trunk - The current stable sfDoctrinePlugin 1.0 that is compatiable with symfony 1.1 I want to propose a new structure. Rename sfDoctrinePlugin/branches/0.1 to sfDoctrinePlugin/branches/0.1-sf1.0 Rename sfDoctrinePlugin/branches/1.0 to sfDoctrinePlugin/branches/1.0-sf1.0 Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.0-sf1.1(I have already done this) Continue development of new version of sfDoctrinePlugin-1.1 compatible with symfony 1.1 in trunk and when it is done: Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.1-sf1.1 The naming pattern is Plugin.Version-sfDependency-Version. Tags would be pretty much the same except with point releases on the version numbers, i.e. sfDoctrinePlugin/tags/1.1.2-sf1.1, sfDoctrinePlugin/tags/1.0.2-sf1.1, etc. I think having this pattern for all plugins would be a good thing. Thoughts? Thanks, Jon -- Jonathan Wage http://www.jwage.com http://www.centresource.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: [Slightly OT] Drupal
OK, thanks, Jonathan. As I mentioned, the client is worried about having to change developers at some point. Now the way I see it, because the bulk of the content will be stored in a database, as long as I create a fairly logical, normalised data model, another developer should be able to take that model and work with it, even if it is not with symfony. Right? Have any of you taken over existing websites/applications and changed from one CMS/framework to another? TIA Tom Jonathan Wage wrote: Drupal is great for one thing, CMS websites. As soon as you go outside of that it becomes increasingly difficult and cumbersome to accomplish custom functionality. I am not arguing that the same end product cannot be accomplished, I am purely speaking from a point of view whether it makes sense or not. PHP covers a wide array of scale when it comes to web applications, which is why so many different tools exist. You have to ask yourself how much custom functionality you will need to build in addition to the native cms functionality you inherit from Drupal. If the answer is none, then I would recommend using Drupal, if the answer is yes then you'll have to gauge how much, how difficult and whether or not you can afford the cost of doing something custom in Drupal. If it is very custom, the cost could end up being greater than just doing it in symfony, and could be more expensive and difficult to maintain. - Jon On Tue, Apr 29, 2008 at 5:17 PM, Tom Haskins-Vaughan [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I have a client who wants a website. He is worried about having to overhaul the website at some point - perhaps with another developer - and so is quite keen to use a commonly used, open source product. I would prefer to use symfony, because I like it and it is infinitely (or almost) flexible. But I'm looking into other solutions, Drupal being one. So, having never used Drupal, would someone who has be able to compare it so symfony (yes, IO know that they're not the same beast)? I mean in terms of data model, forms, routing, etc. Thanks in advance. Tom P.S. I'm in no hurry to leave symfony by the way! -- Jonathan Wage http://www.jwage.com http://www.centresource.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: [Slightly OT] Drupal
I have, and in most cases, changing from one framework to another is not an easy task. It is usually not as simple as copying, pasting, changing, etc. It would require rewriting it completely if you were to move from something like Drupal to symfony. If the client is worried about future expandability and maintainability, then I would say something like symfony would offer you the best options for that. Though, the client must understand that he either pays now or pays later. If you do it in Drupal now, it may cost less now, but cost more in the future when he runs in to expandability and maintainability issues. If you use symfony, it may cost more on the forefront, but it is much more inexpensive to maintain and expand. - Jon On Tue, Apr 29, 2008 at 5:39 PM, Tom Haskins-Vaughan [EMAIL PROTECTED] wrote: OK, thanks, Jonathan. As I mentioned, the client is worried about having to change developers at some point. Now the way I see it, because the bulk of the content will be stored in a database, as long as I create a fairly logical, normalised data model, another developer should be able to take that model and work with it, even if it is not with symfony. Right? Have any of you taken over existing websites/applications and changed from one CMS/framework to another? TIA Tom Jonathan Wage wrote: Drupal is great for one thing, CMS websites. As soon as you go outside of that it becomes increasingly difficult and cumbersome to accomplish custom functionality. I am not arguing that the same end product cannot be accomplished, I am purely speaking from a point of view whether it makes sense or not. PHP covers a wide array of scale when it comes to web applications, which is why so many different tools exist. You have to ask yourself how much custom functionality you will need to build in addition to the native cms functionality you inherit from Drupal. If the answer is none, then I would recommend using Drupal, if the answer is yes then you'll have to gauge how much, how difficult and whether or not you can afford the cost of doing something custom in Drupal. If it is very custom, the cost could end up being greater than just doing it in symfony, and could be more expensive and difficult to maintain. - Jon On Tue, Apr 29, 2008 at 5:17 PM, Tom Haskins-Vaughan [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I have a client who wants a website. He is worried about having to overhaul the website at some point - perhaps with another developer - and so is quite keen to use a commonly used, open source product. I would prefer to use symfony, because I like it and it is infinitely (or almost) flexible. But I'm looking into other solutions, Drupal being one. So, having never used Drupal, would someone who has be able to compare it so symfony (yes, IO know that they're not the same beast)? I mean in terms of data model, forms, routing, etc. Thanks in advance. Tom P.S. I'm in no hurry to leave symfony by the way! -- Jonathan Wage http://www.jwage.com http://www.centresource.com -- Jonathan Wage http://www.jwage.com http://www.centresource.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] is_internal for actions instead of modules?
Hi all, I have some actions that I forward to, but I don't want my users to browse to them (albeit very unlikely since name is unknown..). I know I can make entire modules internal only, but can I do the same with individual actions? Making the action function private just blows it up... Thanks for help, Daniel --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: [symfony-devs] sfDoctrinePlugin SVN organization changes
How are other plugins dealing with Symfony 1.1? (naming of branches and the sort) Jay Jonathan Wage wrote: Hello all, I will be doing some work on the sfDoctrinePlugin for a new version. This will require that we make some changes to the way things are organized in svn. I am going to propose a structure for the branches and tags. Currently we have sfDoctrinePlugin/branches/0.1 and sfDoctrinePlugin/branches/1.0, below is an explanation of what each is currently, and what I want to change it to. sfDoctrinePlugin/branches/0.1 - The very first version of the sfDoctrinePlugin, which is linked to a super outdated version of Doctrine. This branch likely doesn't even work anymore. I would recommend removing it completely? sfDoctrinePlugin/branches/1.0 - The current stable sfDoctrinePlugin 1.0 that is compatible with symfony 1.0 sfDoctrinePlugin/trunk - The current stable sfDoctrinePlugin 1.0 that is compatiable with symfony 1.1 I want to propose a new structure. Rename sfDoctrinePlugin/branches/0.1 to sfDoctrinePlugin/branches/0.1-sf1.0 Rename sfDoctrinePlugin/branches/1.0 to sfDoctrinePlugin/branches/1.0-sf1.0 Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.0-sf1.1(I have already done this) Continue development of new version of sfDoctrinePlugin-1.1 compatible with symfony 1.1 in trunk and when it is done: Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.1-sf1.1 The naming pattern is Plugin.Version-sfDependency-Version. Tags would be pretty much the same except with point releases on the version numbers, i.e. sfDoctrinePlugin/tags/1.1.2-sf1.1, sfDoctrinePlugin/tags/1.0.2-sf1.1, etc. I think having this pattern for all plugins would be a good thing. Thoughts? Thanks, Jon -- Jonathan Wage http://www.jwage.com http://www.centresource.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: [symfony-devs] sfDoctrinePlugin SVN organization changes
Their is no standard rule. It is basically up to the developer :) I think it would be worth enforcing a naming pattern for plugins so that we can have proper naming for multiple versions of plugins which depend on multiple versions of symfony. - Jon On Tue, Apr 29, 2008 at 6:44 PM, Jay Klehr [EMAIL PROTECTED] wrote: How are other plugins dealing with Symfony 1.1? (naming of branches and the sort) Jay Jonathan Wage wrote: Hello all, I will be doing some work on the sfDoctrinePlugin for a new version. This will require that we make some changes to the way things are organized in svn. I am going to propose a structure for the branches and tags. Currently we have sfDoctrinePlugin/branches/0.1 and sfDoctrinePlugin/branches/1.0, below is an explanation of what each is currently, and what I want to change it to. sfDoctrinePlugin/branches/0.1 - The very first version of the sfDoctrinePlugin, which is linked to a super outdated version of Doctrine. This branch likely doesn't even work anymore. I would recommend removing it completely? sfDoctrinePlugin/branches/1.0 - The current stable sfDoctrinePlugin 1.0 that is compatible with symfony 1.0 sfDoctrinePlugin/trunk - The current stable sfDoctrinePlugin 1.0 that is compatiable with symfony 1.1 I want to propose a new structure. Rename sfDoctrinePlugin/branches/0.1 to sfDoctrinePlugin/branches/0.1-sf1.0 Rename sfDoctrinePlugin/branches/1.0 to sfDoctrinePlugin/branches/1.0-sf1.0 Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.0-sf1.1(I have already done this) Continue development of new version of sfDoctrinePlugin-1.1 compatible with symfony 1.1 in trunk and when it is done: Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.1-sf1.1 The naming pattern is Plugin.Version-sfDependency-Version. Tags would be pretty much the same except with point releases on the version numbers, i.e. sfDoctrinePlugin/tags/1.1.2-sf1.1, sfDoctrinePlugin/tags/1.0.2-sf1.1, etc. I think having this pattern for all plugins would be a good thing. Thoughts? Thanks, Jon -- Jonathan Wage http://www.jwage.com http://www.centresource.com -- Jonathan Wage http://www.jwage.com http://www.centresource.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] why having an image_tag ?
Hi all, My HTML guys brought up the question what is really gained by using the image_tag function instead of just using an img tag, especially since the former adds processing time (albeit near zero)... I've been comfortable using the tag function, but now I'm double guessing myself.. Any takes? Daniel --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: [symfony-devs] sfDoctrinePlugin SVN organization changes
For those of you using sfDoctrinePlugin with symfony 1.1 from here: http://svn.symfony-project.com/plugins/sfDoctrinePlugin/trunk, please switch to http://svn.symfony-project.com/plugins/sfDoctrinePlugin/branches/1.0-sf1.1 I will be working in trunk to get the sfDoctrinePlugin 1.1 version prepared and will branch to 1.1-sf1.1 as soon as it is complete and stable. Thanks, Jon On Tue, Apr 29, 2008 at 6:52 PM, Jonathan Wage [EMAIL PROTECTED] wrote: Their is no standard rule. It is basically up to the developer :) I think it would be worth enforcing a naming pattern for plugins so that we can have proper naming for multiple versions of plugins which depend on multiple versions of symfony. - Jon On Tue, Apr 29, 2008 at 6:44 PM, Jay Klehr [EMAIL PROTECTED] wrote: How are other plugins dealing with Symfony 1.1? (naming of branches and the sort) Jay Jonathan Wage wrote: Hello all, I will be doing some work on the sfDoctrinePlugin for a new version. This will require that we make some changes to the way things are organized in svn. I am going to propose a structure for the branches and tags. Currently we have sfDoctrinePlugin/branches/0.1 and sfDoctrinePlugin/branches/1.0, below is an explanation of what each is currently, and what I want to change it to. sfDoctrinePlugin/branches/0.1 - The very first version of the sfDoctrinePlugin, which is linked to a super outdated version of Doctrine. This branch likely doesn't even work anymore. I would recommend removing it completely? sfDoctrinePlugin/branches/1.0 - The current stable sfDoctrinePlugin 1.0 that is compatible with symfony 1.0 sfDoctrinePlugin/trunk - The current stable sfDoctrinePlugin 1.0 that is compatiable with symfony 1.1 I want to propose a new structure. Rename sfDoctrinePlugin/branches/0.1 to sfDoctrinePlugin/branches/0.1-sf1.0 Rename sfDoctrinePlugin/branches/1.0 to sfDoctrinePlugin/branches/1.0-sf1.0 Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.0-sf1.1(I have already done this) Continue development of new version of sfDoctrinePlugin-1.1 compatible with symfony 1.1 in trunk and when it is done: Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.1-sf1.1 The naming pattern is Plugin.Version-sfDependency-Version. Tags would be pretty much the same except with point releases on the version numbers, i.e. sfDoctrinePlugin/tags/1.1.2-sf1.1, sfDoctrinePlugin/tags/1.0.2-sf1.1, etc. I think having this pattern for all plugins would be a good thing. Thoughts? Thanks, Jon -- Jonathan Wage http://www.jwage.com http://www.centresource.com -- Jonathan Wage http://www.jwage.com http://www.centresource.com -- Jonathan Wage http://www.jwage.com http://www.centresource.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: sfDoctrinePlugin SVN organization changes
Please, allow some kind of download, ...for any version... I would like to try it (above 0.1 of course) and can't get it through svn, and shouldn't get it through pear. Is there any chance? On Apr 29, 6:37 pm, Jonathan Wage [EMAIL PROTECTED] wrote: Hello all, I will be doing some work on the sfDoctrinePlugin for a new version. This will require that we make some changes to the way things are organized in svn. I am going to propose a structure for the branches and tags. Currently we have sfDoctrinePlugin/branches/0.1 and sfDoctrinePlugin/branches/1.0, below is an explanation of what each is currently, and what I want to change it to. sfDoctrinePlugin/branches/0.1 - The very first version of the sfDoctrinePlugin, which is linked to a super outdated version of Doctrine. This branch likely doesn't even work anymore. I would recommend removing it completely? sfDoctrinePlugin/branches/1.0 - The current stable sfDoctrinePlugin 1.0 that is compatible with symfony 1.0 sfDoctrinePlugin/trunk - The current stable sfDoctrinePlugin 1.0 that is compatiable with symfony 1.1 I want to propose a new structure. Rename sfDoctrinePlugin/branches/0.1 to sfDoctrinePlugin/branches/0.1-sf1.0 Rename sfDoctrinePlugin/branches/1.0 to sfDoctrinePlugin/branches/1.0-sf1.0 Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.0-sf1.1(I have already done this) Continue development of new version of sfDoctrinePlugin-1.1 compatible with symfony 1.1 in trunk and when it is done: Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.1-sf1.1 The naming pattern is Plugin.Version-sfDependency-Version. Tags would be pretty much the same except with point releases on the version numbers, i.e. sfDoctrinePlugin/tags/1.1.2-sf1.1, sfDoctrinePlugin/tags/1.0.2-sf1.1, etc. I think having this pattern for all plugins would be a good thing. Thoughts? Thanks, Jon -- Jonathan Wagehttp://www.jwage.comhttp://www.centresource.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Security: How can I restrict an action to the owner only?
Security: How can I restrict an action to the owner only? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: sfDoctrinePlugin SVN organization changes
It is only available via svn currently :( Sorry What is the problem with getting it via svn? - Jon On Tue, Apr 29, 2008 at 7:28 PM, arhak [EMAIL PROTECTED] wrote: Please, allow some kind of download, ...for any version... I would like to try it (above 0.1 of course) and can't get it through svn, and shouldn't get it through pear. Is there any chance? On Apr 29, 6:37 pm, Jonathan Wage [EMAIL PROTECTED] wrote: Hello all, I will be doing some work on the sfDoctrinePlugin for a new version. This will require that we make some changes to the way things are organized in svn. I am going to propose a structure for the branches and tags. Currently we have sfDoctrinePlugin/branches/0.1 and sfDoctrinePlugin/branches/1.0, below is an explanation of what each is currently, and what I want to change it to. sfDoctrinePlugin/branches/0.1 - The very first version of the sfDoctrinePlugin, which is linked to a super outdated version of Doctrine. This branch likely doesn't even work anymore. I would recommend removing it completely? sfDoctrinePlugin/branches/1.0 - The current stable sfDoctrinePlugin 1.0 that is compatible with symfony 1.0 sfDoctrinePlugin/trunk - The current stable sfDoctrinePlugin 1.0 that is compatiable with symfony 1.1 I want to propose a new structure. Rename sfDoctrinePlugin/branches/0.1 to sfDoctrinePlugin/branches/0.1-sf1.0 Rename sfDoctrinePlugin/branches/1.0 to sfDoctrinePlugin/branches/1.0-sf1.0 Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.0-sf1.1(I have already done this) Continue development of new version of sfDoctrinePlugin-1.1 compatible with symfony 1.1 in trunk and when it is done: Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.1-sf1.1 The naming pattern is Plugin.Version-sfDependency-Version. Tags would be pretty much the same except with point releases on the version numbers, i.e. sfDoctrinePlugin/tags/1.1.2-sf1.1, sfDoctrinePlugin/tags/1.0.2-sf1.1, etc. I think having this pattern for all plugins would be a good thing. Thoughts? Thanks, Jon -- Jonathan Wagehttp://www.jwage.comhttp://www.centresource.com -- Jonathan Wage http://www.jwage.com http://www.centresource.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Is current user allowed to perform X action?
How can it be quickly tested if current user will be able to perform
an specific action?
I know it´s possible to test for a credential, and also load the
configured credential restrictions, but there should be some how to
test for
Is current user allowed to perform X action?
$user-isAuthenticated()
$user-hasCredentialsFor('module/action')
Isn't anything like it?
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~--~~~~--~~--~--~---
[symfony-users] Re: Cookie user session
You should check out sfGuard, for the Remember me feature. On Apr 29, 11:03 am, DC [EMAIL PROTECTED] wrote: I'm trying to keep users logged in for 2 weeks. I've changed the timeout setting to 2 weeks (sf_timeout: 1209600), but the symfony cookie expires at the end of the session. Any way I can fix that? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: why having an image_tag ?
I like the neatness of it. Especially when combined with a link_to tag. I'd rather not put html into a link_to so this helps me here. Another reason, I guess, is that you could move the image folder - for whatever reason - and then just change the config rather than going through all your img tags and doing it by hand/script. Other than that, I can't think. Richtermeister wrote: Hi all, My HTML guys brought up the question what is really gained by using the image_tag function instead of just using an img tag, especially since the former adds processing time (albeit near zero)... I've been comfortable using the tag function, but now I'm double guessing myself.. Any takes? Daniel --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
[symfony-users] Re: why having an image_tag ?
...and some developers don't like php in HTML tags ie. messy: img src=/images/myimage.gif class=?= $class ? / neat... being php only (matter of preference really): ?= image_tag(myimage.gif,class=$class); ? 2008/4/30 Tom Haskins-Vaughan [EMAIL PROTECTED]: I like the neatness of it. Especially when combined with a link_to tag. I'd rather not put html into a link_to so this helps me here. Another reason, I guess, is that you could move the image folder - for whatever reason - and then just change the config rather than going through all your img tags and doing it by hand/script. Other than that, I can't think. Richtermeister wrote: Hi all, My HTML guys brought up the question what is really gained by using the image_tag function instead of just using an img tag, especially since the former adds processing time (albeit near zero)... I've been comfortable using the tag function, but now I'm double guessing myself.. Any takes? Daniel -- Charles Hilditch Web Developer Mob: 0415 166 137 [EMAIL PROTECTED] http://www.crh-systems.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~--~~~~--~~--~--~---
