Things like that Alistair exists in many projects, people think that core
team MUST be pay attention only for he problems and issues.
I hope that Fabien and Core team leave this people/things to back and go
ahead with this great framework.
So, thank you Fabien, Francois, Greg, and core team for your work!
On Sat, Apr 5, 2008 at 9:20 AM, Alistair Stead <
[EMAIL PROTECTED]> wrote:
> Fabien, comments like that must really get you down....
> He could have at least started with "Thanks for all the months of hard
> work building an open source project and providing such quick access to
> support and information" There are not many open-source projects that come
> close to the level of support of symfony.
>
> But thanks from me anyway...
>
> On 05/04/2008, Fabien POTENCIER <[EMAIL PROTECTED]>
> wrote:
> >
> >
> > Joe Kelsey wrote:
> > > You should definitely remove the completely incorrect idea of the copy
> > > step. There seems to be some major problems with the reasoning of how
> > > plugins work from the sensio crowd.
> >
> >
> > If you don't like Sensio contributions, just don't use them.
> >
> > I really think you need to do your homework, try to read the symfony
> > book, try to understand the Open-Source philosophy, try to find
> > solutions to problems you might have, and perhaps contribute back to the
> > community.
> >
> > I'm very sorry you don't get it. But perhaps, someone will explain you
> > what's wrong with your reasoning ;)
> >
> >
> > Fabien
> >
> >
> > > I cannot figure out how they
> > > produced the plugins to begin with when the keep talking about copying
> > > things that happen automatically.
> > >
> > > Many parts of the sfGuardPlugin involve things that just happen, but
> > > the instructions keep talking about copying things.
> > >
> > > Now what I want to do is to integrate the sfGuardUser with my own
> > > "user profile". There is some talk in the plugin README, but it is
> > > really confusing. I want to have the various tables "automatically"
> > > pick up the user name instead of just picking up the user_id. The
> > > README needs to be explicit about which file in the plugin to read to
> > > steal of copy the code from in order to ahve your own templates and
> > > actions do the same thing the the Guard Plugins do. It takes a little
> > > while to find this stuff and some pointers would sure help out. I
> > > will find it eventually.
> > >
> > > Also, when I first started using the Guard Plugin, the routing just
> > > raised big errors, so I changed it to explicitly route everything.
> > > Did that get fixed with the whole "beta2" release or is it still
> > > broken? I had so much trouble with it that I just disabled it and put
> > > in the explicit routing.
> > >
> > > /Joe
> > >
> > >
> > > On Apr 2, 5:48 pm, markchicobaby <[EMAIL PROTECTED]> wrote:
> > >> Or would it be better to keep the copy step, but rename the sfGuard
> > >> fixtures back to fixtures.yml.sample.
> > >>
> > >> This would encourage people to use different passwords from the
> > >> inbuilt, in their own versions. (Or is the password tied to the SHA
> > >> and salt, methinks it might be necessary to change it after install
> > >> anyway via the application?)
> > >>
> > >> Anyway, up to you.....
> > >>
> > >> On Apr 3, 2:29 am, markchicobaby <[EMAIL PROTECTED]> wrote:
> > >>
> > >>> Sorry, I cleared my Symfony cache and the error complaining about a
> > >>> missing module went away. I guess the 'symfony cc' could be earlier
> > a
> > >>> bit earlier in the instructions, just before the data load.
> > >>> Unfortunately I'm one of those people who follow instructions to the
> > >>> letter!
> > >>> Now instead I get a duplicate record error: I've tried dropping all
> > >>> tables and reloading, so they definitely start completely empty:
> > >>> Looks like there is no need to copy the fixtures file anymore as it
> > >>> seems to find both of them? Now that would be why the one in the
> > >>> plugins directory is missing the .sample extension. So can the copy
> > >>> fixtures step be removed from the instructions?
> > >>> C:\>symfony propel-load-data frontend
> > >>>>> propel load data from "C:\...\sfGuardPlugin\data\fixtures"
> > >>>>> propel load data from "C:\...sfprojects\myapp\data\fixtures"
> > >>> [PropelException]
> > >>> Unable to execute INSERT statement. [wrapped: Could not execute
> > >>> update [Native Error: Duplicate entry 'admin' for key 2] [User Info:
> > >>> INSERT INTO sf_guard_user (USERNAME
> > >>> ,ALGORITHM,SALT,PASSWORD,CREATED_AT,IS_SUPER_ADMIN) VALUES
> > >>>
> > ('admin','sha1','38944634f8dab81b9835ab94a81bb729','7be3886ef6a7cda7d7b06829bce5ceac85e12334','2008-04-03
> > >>> 01:23
> > >>> :53',1)]]
> > >>> On Apr 3, 1:57 am, Fabien POTENCIER <[EMAIL PROTECTED]
> > >>> project.com> wrote:
> > >>>> markchicobaby wrote:
> > >>>>> Thanks Fabien, while you've got it top of mind could you also make
> > >>>>> these corrections:
> > >>>>> 1. The command
> > >>>>> cp plugins/sfGuardPlugin/data/fixtures/fixtures.yml.sample data/
> > >>>>> fixtures/sfGuard.yml
> > >>>>> is still incorrect. The file "fixtures.yml.sample" is actually
> > called
> > >>>>> "fixtures.yml"
> > >>>> fixed
> > >>>>> 2. The dataload needs to be after the modules are enabled. It
> > fails
> > >>>>> unless the modules are enabled which in the instructions is the
> > next
> > >>>>> step, so its out of sequence.
> > >>>> No, you don't need to enable any module to launch the data load.
> > Can you
> > >>>> give the error message you have?
> > >>>>> 3. Finally the dataload assumes both a backend and fronted
> > >>>>> application, ie, it assumes all modules are enabled, whereas the
> > >>>>> instructions indicate the modules are optional. The dataload
> > fails
> > >>>>> with a nasty error message if any one of the modules isn't
> > enabled.
> > >>>> Same as above.
> > >>>> Fabien
> > >>>>> On Apr 2, 8:00 pm, Fabien POTENCIER <[EMAIL PROTECTED]
> > >>>>> project.com> wrote:
> > >>>>>> markchicobaby wrote:
> > >>>>>>> Hi myself and a few others (see forum thread:
> > >>>>>>>
> > http://www.symfony-project.org/forum/index.php/m/32413/?srch=sfguard+...
> > >>>>>>> )
> > >>>>>>> are experiencing problems with sfGuard installation
> > instructions.
> > >>>>>>> Is this a bug or is it the installation instructions? (I can
> > confirm
> > >>>>>>> that at least this line on those instructions is incorrect as
> > the
> > >>>>>>> source file is incorrectly named. Also the fixtures target
> > directory
> > >>>>>>> doesn't exist unless a user specifically creates it:
> > >>>>>>> cp plugins/sfGuardPlugin/data/fixtures/fixtures.yml.sample data/
> > >>>>>>> fixtures/sfGuard.yml
> > >>>>>>> )
> > >>>>>> I've updated the README file.
> > >>>>>>> I've also had problems getting the propel-insert-sql task to run
> > (it
> > >>>>>>> reports that it ran with no errors, but no tables are created)
> > >>>>>> Check that your propel.ini file references correctly your
> > database settings.
> > >>>>>> Fabien
> > >>>>>>> Should I log these as bugs, or is it just the docs.
> > >>>>>>> M
> > > >
> > >
> > >
> >
> >
> > > >
> >
--
Lucas Stephanou
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" 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-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
