Thanks for the kind reply Flukey, When I had originally found this plugin the documentation on the plugins page was outdated. Once I tried tried to fork the plugin because it seemed it was only updated to symfony 1.2 I was then contacted by the author. He notified me that the plugin is maintained on github so I then in turn removed my fork. I have followed 3 different readme's and tutorials. The original readme from the author, the tutorial in the symfony book, and a 3rd party tutorial on a blog I found. All of them returned the same results when using the Demo application. I have even removed all files and did a fresh install. I don't know how my config could be different but it seems I ran into this error.
I am sorry for sending this request to the wrong mailing-list. However it does seem that everyone is quick to say "look at the code and fix it yourself". Because of this I feel that symfony is not the framework I should use for my projects. @Fabrice I have only received a response from you in regards to the forking of the plugin. When the emails started about this error I received no more responses. I did however receive an email saying "Feel free to make changes yourself and fork the plugin on git.". I am not wanting to change your plugin because I am not sure if there is a reason you are trying to directly call an abstract method? I am no php guru so if there was a reason for this I didn't want to change it. Anyways, thanks for your time. I see no need to continue arguing on this matter. On May 20, 11:58 am, Fabrice Bernhard <[email protected]> wrote: > As the lead author of the plugin I also have to say that I answered > all your mails. It seems quite sure Brian that your problem is not a > bug but an error in your configuration. To understand further your > problem would need me to dive deeper into your project and would take > time. ...since you are not my mother I cannot do that on my spare > time :-) I can do consulting for you if it is critical. > > Thanks Flukey for defending the documentation of the plugin. I've > spent whole days writing the blog chapter and translating it and I am > happy to see that it was useful for most people. > > Cheers ! > > Fabrice > > On May 20, 4:05 pm, Flukey <[email protected]> wrote: > > > > > I'm sorry, but I feel the need to pipe up and say something. > > > First of all, that plugin has a lot of documentation, especially when > > compared to other plugins! I've used this plugin and followed the > > guide and I had no problems at all. > > > Second of all, this is a place to discuss the development of symfony > > and not for any bugs you're having with plugins. Please use the normal > > symfony mailing list, forums or stackoverflow. Of course, you could do > > one thing which most developers don't bother with and instead just > > automatically ask someone else to fix, try looking at the code. I'm > > sure you'll find what the error is in the end. (sorry to patronise) > > > Furthermore, if you fix the bug, inform the author and get the > > documentation changed....better to keep contributing and helping out > > others who might get the same problem. > > > Have a good day. > > > On May 19, 9:53 pm, jostster <[email protected]> wrote: > > > > The documentation is VERY lacking and I have looked at all the sites > > > possible to assist with this plugin. I have even removed symfony > > > completely and done a fresh install and project and still receive the > > > error. I forgot to mention this error happens when using the demo > > > however using the regular tutorial for the auth module just results in > > > an error stating that the user Facebook_ already exists. > > > > On May 19, 3:41 am, Fabrice Bernhard <[email protected]> wrote: > > > > > Hi Brian, > > > > > I think you spammed every possible bugtracker/mailing-list/plugin > > > > author with your bug ! :-) > > > > > Since many people use the plugin without having this blocking problem, > > > > I think you just misconfigured the plugin. Please read carefully the > > > > documentationhttp://www.symfony-project.org/more-with-symfony/1_4/en/12-Developing... > > > > and check the configuration. Don't hesitate to dive into the code too. > > > > But try harder before reporting bugs, it will make your bug reports > > > > all the more precise and the solution to your problem will come much > > > > faster ! > > > > > Cheers, > > > > > Fabrice > > > > > On May 18, 9:31 am, "[MA]Pascal" <[email protected]> wrote: > > > > > > Hi, > > > > > > This plugin has his own bug tracker > > > > > athttp://labs.theodo.fr/projects/sffacebookconnect/issues > > > > > , you should report your issue there, or ask in symfony-users mailing- > > > > > list (http://groups.google.com/group/symfony-users) and if critical > > > > > contact plugin authors mentioned in this > > > > > pagehttp://www.symfony-project.org/plugins/sfFacebookConnectPlugin > > > > > > Regards, > > > > > [MA]Pascal > > > > > > On May 18, 3:49 am, jostster <[email protected]> wrote: > > > > > > > Anyone able to give any thoughts on how to resolve this error? > > > > > > >http://forum.symfony-project.org/index.php/t/27450/ > > > > > > > For those that don't want to click it, here is the text. > > > > > > > I downloaded the version from SVN but when I login with my facebook > > > > > > info I get this error > > > > > > > Quote: > > > > > > > Strict Standards: Non-static method > > > > > > sfFacebookGuardAdapter::getUserProfileProperty() should not be > > > > > > called > > > > > > statically, assuming $this from incompatible context in /home2/ > > > > > > ameriee2/aksymfony/plugins/sfFacebookConnectPlugin/li b/ > > > > > > sfFacebookApplicationFilter.class.php on line 25 > > > > > > > Fatal error: Cannot call abstract method > > > > > > sfFacebookGuardAdapter::getUserProfileProperty() in /home2/ameriee2/ > > > > > > aksymfony/plugins/sfFacebookConnectPlugin/li b/ > > > > > > sfFacebookApplicationFilter.class.php on line 25 > > > > > > > However if I hit refresh in the url bar it will login me in and the > > > > > > error will go away. Any ideas? > > > > > > > -- > > > > > > 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 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 > > > > > > athttp://groups.google.com/group/symfony-devs?hl=en > > > > > > -- > > > > > 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 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 > > > > > athttp://groups.google.com/group/symfony-devs?hl=en > > > > > -- > > > > 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 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 > > > > athttp://groups.google.com/group/symfony-devs?hl=en > > > > -- > > > 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 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 > > > athttp://groups.google.com/group/symfony-devs?hl=en > > > -- > > 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 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 > > athttp://groups.google.com/group/symfony-devs?hl=en > > -- > 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 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 > athttp://groups.google.com/group/symfony-devs?hl=en -- 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 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
