dimitrios
-
Posts
18 -
Joined
-
Last visited
-
Days Won
1
Recent Profile Visitors
2,055 profile views
dimitrios's Achievements
Jr. Member (3/6)
35
Reputation
-
Hi @nfil I just tested up to API version v3.3, so I don't believe this is the problem. Is the site SSL enabled?
-
No problem nfil. On settings -> advanced, it is the drop-down by the name Upgrade All Calls.
-
You are free to test it with the latest API version before changing it. As for the login settings, you will first have to add product "Facebook Login".
-
Hello, this module has been updated to conform to recent Facebook regulations that won't allow publishing content on a user profile. Instead, a post may be published on a Facebook page by the Facebook page only. To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers: Minimum Required Facebook App configuration: on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. You may also view the revised first post of this topic. Thank you for your valuable input and I hope this update helps! Kind regards, Dimitrios
-
Hello, you can update this module, because the issue has been resolved with the next version of php-graph-sdk. Then, remember to go to your app in Facebook for developers -> Facebook Login -> Settings and add "http://www.example.com/processwire/page/" to the list of Valid OAuth Redirect URIs. I only used it because I was allowed to, until recently; it was convenient to go back to the exact page we were editing.
-
Hello, the issue has been resolved. To anyone facing the same problem, do NOT set permission 'page-edit-created' role-wide; instead, add it as an additional edit permission in each template relevant to the role. Thank you- 3 replies
-
- 4
-
-
-
- tags
- page-edit-created
- (and 3 more)
-
Hello, I meet the requirements you mention, and the role in question has edit and create page permissions on the corresponding pages and can add children under the parent. Are the above all you had to take care of, for the non superuser role to work properly?
-
Hello, I have created a field of type Page Reference and input field type Page Auto Complete, so that users of role 'writer' can add new tags to their articles. However, only a superuser can add new tags through the field, even though 'writer' roles have the permission to create pages of template 'tag', and the permission to add children in the parent template. New tags in the Page Tree can be added normally. Is there something I am missing?
-
Hello @Hurme, on the Facebook for developers page, in your app's settings, provide the App domains field with your domain. I believe this is the only problem.
-
That's great @palacios000. Thanks for posting the solution.
-
Hi @palacios000, the facebook app should work in development mode. Is everything in Settings->Advanced configured properly?
-
Hello, this module has been updated and it is now compatible with Graph API version 2.10. Parameters 'description' and 'name' are not supported by the new Graph API version. Therefore, fields for description and name cannot be provided anymore.
-
Hello, thank you for your kind words @alexmercenary, I'm glad it was of use to you. @flydev, that is absolutely right, you need to create a checkbox field as with any other field or use an existing one and insert it into the template.
-
Hello, I will consider it, although I am on a tight schedule lately. However, I'm not sure if it would be wise, because the old Facebook PHP SDK v3 is now deprecated, so there will be zero maintenance from their part.
-
Hello Juergen, I am sorry for such a late answer. You are right, this is not needed since PW manages the session. I will try to test this module with various PW versions and update it. Thank you for your post!
