For the screencast, you can take a video with your phone of how you will be posting the content to your site. JFBConnect doesn't support automatically posting new products from Virtuemart, but you would be able to use the "Create Post" button from our 'social toolbar' on the front-end of your site.
So, a good video would be of you:
* Authenticating with Facebook on the front-end of your site
* Noting that the social toolbar only shows to administrators on the site, such as yourself
* Going to a product page
* Clicking the "Create Post" button
That's all that's needed and it can be a 20-30s video without any editing.
I hope that helps, but if you need anything else, just let me know.
The App Review process is required by Facebook to use some specific permissions and features on your site. The review process can be started from the Facebook Developer Area by clicking into your app and going to the App Review -> Requests tab.
The process of App Review is explained on the page itself, but we also have an overview that you can view in our blog post, Facebook App Review Explained. Basically, you need to explain to Facebook how you want to use the manage_pages permission on your site. The answer and what you need to explain is:
We are using the manage_pages permission to post content from our site to our Facebook Page. We are not asking visitors to our site for this permission. It will only be requested of administrators of our Facebook app.
Supporting pictures and other information you provide will help get it approved.
I hope that helps,
If things change drastically, we'll likely write up a blog post or even a newsletter. Many rollouts of changes (even if they have a specific date announced) actually happen over a matter of weeks and it's not always a binary "This broke, that works". Due to the rollout, what still works for us may have broken for some users and *will* break for us, eventually.
It's more than a bit annoying working with the review process, but we do what we can to stay on top of things and keep everyone aware. We do have many apps that we have setup to test with to try and get a feel for which way the tide is going (is this a good change or a bad one?), but even then, we miss things coming down the pike. One of our best resources is our users to report problems they encounter so we can investigate more. While we have tens of apps to test with, our user base is in the thousands, which is a much better sample size.
I hope that helps explain. Please don't hesitate to ask any questions, report any issues or provide any feedback!
I understand your frustration, though I don't have anything great to tell you. We were just denied access to the LinkedIn Developer Marketing Program which is necessary for some features. We're going back and forth with them on the process to reapply (which they don't make easy). We've also been denied in the past for some permissions, but with further explanation and attempts have been approved. In some cases, we've asked for a permission even when we thought we hadn't submitted much information and it's sailed right through without any issues.
I looked through your past posts and saw you had asked a question about app review back in late 2018. Unsure if you've been struggling with the whole time since, but if there's anything you want to share with what you've tried, we'll gladly look over it to let you know any suggestions we may have.
For 1 & 2, it sounds like you have a good grasp on how it should all work. I understand your confusion with the JReviews plugin and that's on our end. Not all Open Graph plugins have the ability to autopost. There are some object types (like a user profile in JomSocial for example) that just shouldn't be auto-posted normally. Currently, our JReviews plugin does not support autoposting either.
With that said, JReviews is built on top of Joomla's content system. Our Open Graph - Content plugin should be able to do what you're looking for here, and we know many users who are using the content plugin to do so. I'd recommend setting up objects using the Open Graph - Content plugin to point to categories that your JReviews listings go in. Then, you can setup autoposting to use those content categories.
As mentioned, that method has worked for other users. However, if you run into issues or limitations doing it that way, please let us know what they are and we can investigate adding autoposting to the JReviews plugin. It's do-able, just something we haven't spent time on because it hasn't been necessary.
3) The choice of Autopost Plugin or Autopost Object is meant to make setting things up easier. If, by chance, you want all new articles on your site within Joomla content to be autoposted, you can use the "Autopost Plugin" option. That will post everything created, whether you specifically created an object type for the article or not. Autopost Object is more targetted so that you can setup an object type for category 'a'. Then, when new content is created in that category (or it's subcategories), that content would be autoposted. Content in an unrelated category 'z' would not be autoposted.
4) The access level setting lets you choose the content-level access setting that should be posted. For example, if you create a new article with an Access Level of 'Registered', then the Autopost feature will only post that content if it's access level setting is also Registered. Most users use the 'Guest' setting for their content, meaning that anyone visiting the site can read the article. In Autoposting, they also use Guest so that new content is automatically posted. With those settings, In the event you want to create an article that's only available to users that login, you would set the article's access level to 'Registered' or 'Subscription' and it would not be automatically posted.
I hope that helps explain, but if you need anything else, please let me know!
Thanks so much for your details on how you set things up and got it all working together.
We agree that there are a lot of options in JFBConnect. We are always working to provide the features users want, while at the same time limiting too many settings to prevent it from getting impossibly complex. It's a tough balancing act.
If you have any feedback on how we can improve things, whether in our documentation, the admin area or elsewhere, please let us know. We're always listening!
Can you post the listing page you're talking about? I can't find a viewable page on your site that doesn't automatically take me to the login page. Seeing how things are setup will help.
I'm not exactly sure how K2 works with Read More links, but a Joomla article Read More link to a registered article will redirect the user to the login page and the URL will have a special parameter like ?return=Lz3lkjab8asl
That 'return' parameter is used by Joomla and JFBConnect to know where to send the user after they authenticate. Feel free to test that with a Joomla article with a teaser intro to see how it works. I believe K2 does the same thing. JFBConnect should respect those return parameters in both cases.
I hope that helps,
All good questions, Nick. All good questions. We can tell you what we think will happen, but Facebook is very opaque about a lot of these things and, unfortunately, we have to wait until whatever they announce happens to actually know how it affects things.
Your Channel in JFBConnect definitely won't go away. We store the information about the Channel in your database so you won't have to reconfigure JFBConnect. When the permission goes away, 1 of 2 things is going to happen:
* Nothing. Since JFBConnect already has the Page Details *and* you've approved the 'publish_pages' permission (which isn't going through the same change as manage_pages that we're aware of), things may just work. If you wanted to publish to a new Page, you would need to get the publish_pages permission.
* Publishing and Reading from your Page will stop working. Once you get approved for that permission, you'll need to authenticate on the front-end again and JFBConnect will get back to working as normal.
App Review is a big pain, we'll agree. However, we'd recommend starting the process for the manage_pages and publish_pages permission when you get a chance to ensure you have what you need for features and functionality to keep working properly.
I hope that helps!
You're right about the App Review process is a mess. We've created blog posts, added an 'App Review' section in the admin area of the app itself, and tried to help support our users in every way we can. The unfortunate bit is that there isn't a one-size fits all solution to how to submit your app. We've guided users in the forums with a canned response in the past that has garnered responses from Facebook of approval, denial and requests for more information. The app approval process is done by different reviewers on FB's end each time and there is not the consistency you or I would like.
As for what I can tell you, many people have gone through the review process using just a screen shot and video of the administrator area. For the Channels feature, I'd recommend describing it as:
"We will use this feature to post content from the Facebook Administrators of our account to our own Facebook Pages. We will not be asking regular users for the manage_pages permission as it will only be for our administrators."
We've heard of good results with that, but again, your results may differ. We've heard of many times where someone is denied and then resubmits with almost the exact same request and is approved.
I hope that helps, but either way, please let us know how your submission goes.
I would think that the Access Level feature would publish any articles that are equal to the access level specified. Access Levels cannot have an hierarchy,
You're correct. I was thinking of User Levels, not access levels. If you set the content to a specific Access Level then it should only be published if that Access Level is allowed for that channel.
The issue is that if you enable the Messenger plugin, the script that is placed in the body of the page is overriding the script that is needed for the Autopost to work properly.
You are correct. We'll update our Autotune detection mechanism. The Facebook Messenger feature was recently released and we didn't update Autotune appropriately. If you get a pass with Messenger disabled, then everything will be ok when it's enabled (even if Autotune is telling you otherwise for now).
Turn Messenger off and run the Error Check again and it works.
This part I'm confused on. We'll absolutely agree that Autotune will fail right now with Messenger enabled. However, that really shouldn't affect autoposting. However, if you're saying it is, please let us know and we can investigate further. Also, let us know if you're talking about autoposting or using the 'Create Post' button from the social toolbar to manually post. Any details will help us understand further.
Maybe the Autopost recurses through sub-categories? I didn't test that with a working site. I am happy leaving it as is because I don't want too many sub-categories. It would make the site look ugly if someone start browsing through categories.
This is definitely correct. An object you create will recurse through categories *and* the 'best' object will be applied. By that, I mean you can create one more general object for your root category. That will apply to all categories on your site, the root on down. If you create an object for a specific subcategory though, that object will take priority and be applied to that sub-category and it's children. That system allows you to create only the objects that are needed.. one or maybe 2 generic objects to cover most of your site, and then a targeted object for specific areas of your site you want treated differently.
Your doing better than us After nudging them, our application was declined due to our use case. Unfortunately, we submitted it back in June (and honestly, pretty quickly to get it in) and don't even remember what we described our Use Case as.. We're trying to work through that now to resubmit.. but they've thrown up other hurdles.
I don't think the 'Ad Account' area has any relevance to the permissions and API we'd need to post content.
If you update things and can send us FTP credentials, let us know and we'll gladly help however we can. Another option would be to send us your Client ID and Secret Key and update your app with a callback URL we can use. That way, we can do development locally (which is easier) and we won't have admin access to your site (which is understandably not desired).
If you'd prefer that, setup a callback URL like below (note .test, which is not normally valid on the 'net but works for development). You'd need to set this in the 'Auth' section of your app:
http://www.sourcecoast.test/index.php?o … r=linkedin
Once that's set, Private Message the client_id and secret key and we'll get to work. When done, you can always reset/change the secret ID.
Hopefully, we'll get our own access soon
Please see my post in your other thread.
I apologize greatly. I talked with Melissa who developed the Channels feature and was informed about the Access Level setting in the Channels setting. This feature was added over this Summer and I simply wasn't aware of it.
The Access Level feature should do what you're looking for. Basically, the Access Level you set in the Channel will be checked against the Article's access level. If the Articles access level is *lower* or equal to the setting for the Channel, it will be published.
We looked through the code today and the functionality should work. However, we noticed there's one possible complication if you've created additional access levels where some access are higher and lower than the default 'Registered' view. If that's the case, let us know and we can investigate further if there is indeed a publishing issue when the Access Level in the channel is set to a specific value.
Again, I apologize for making you go off on the tangent of creating new categories. The good news is that the method you want to use is in JFBConnect and, if there are issues with our implementation, we'll gladly help you get them fixed.
It looks like you've got everything right. LinkedIn did change their behavior earlier this year and we support the 'old' behavior still. We applied for the LinkedIn Marketing Developer Program back in June and are still in Review.. which kinda sucks. There's no reason as to why and it's a bit of a black box, but we've sent our support tickets asking to get it out of the molasses it's in.
With that said, after they switched to requiring the new Marketing Developer Program requirement, the 'old' way continued to work for some time. I'm not sure when that was blocked, but it seems like the current JFBConnect method doesn't work even if you are approved for the MDP.
Unfortunately, the documentation for the MDP is either hidden (possibly unlocked when we are approved) or incredibly hard to find. If you're interested in providing FTP access to your site, we'll gladly investigate further to see if we can figure out a solution. If so, please Private Message me by clicking the mail icon to the left to send Joomla administrator and FTP credentials so we can modify code.
We just submitted a support ticket to LinkedIn tonight, so it's possible we'll get our access soon.. we'll have to see.
JFBConnect is fully compatible with the the newest versions of the Facebook API. As a matter of fact, all apps that are created automatically are forced to use the latest version of the app and can't downgrade to older versions.
We usually set JFBConnect up to use the older version of the APIs as the older versions usually allow more access. That's going away slowly, but it doesn't hurt to set to the older version as it allows JFBConnect to access some of these 'older' features on apps that were created long ago, but as mentioned, we're still compatible with the latest releases of the API that Facebook may force your app to use anyways.
I hope that all makes sense to explain the background.. you can set the 'Upgrade All Calls' setting however you want and you likely won't see any difference in behavior.
You can get your Subscriber ID by going to the My Account -> My Profile menu item in the top right of this site. The Subscriber ID is a 32-character string you add to JFBConnect to enable some features like the automatic configuration tool.
I'm sorry for the delay and confusion. We used to have an affiliate program for our products, but we discontinued that in January of this year. It seems like Stack Ideas (developers of Easy Social) have not updated the link in their extension yet, which is why it is leading to an error page.
You can read more about JFBConnect or purchase it at the link below:
I hope that helps answer your question, but should you need anything else, please let us know.
In the Facebook App Developer Area, click into your app. In the top right corner, there should be a switch for "Live" or "Development Mode". Switch that to "Live" so it's accessible by everyone.
I hope that helps,
I'm sorry to hear we don't have the feature you're looking for. We've had autoposting built-in to JFBConnect for more than 4 years now and, honestly, access-level auto-posting has never been requested. Generally speaking, as noted above, the posting of all content (registered or public, but not 'special') has worked for our users as it serves the purpose of letting viewers on social media know that new content is available and to come to the site. If they need to register to see it, that's a site-specific choice, but the posting can be beneficial in gaining new users.
I have developed this site to be as simple as possible for the end-users, which are not technical people.
I'm unsure how you are planning to post content. JFBConnect Channels are meant to post to your websites Facebook Page. The way you describe your setup, it sounds like users on your site will be creating content and that will be posted to your Facebook Page. If that's the case, that should still work, and I'm not sure how access levels are easier to understand than categories.
Again, if you can provide more details on how your site is setup, how content is generated and how you expect it to be posted to social media, that would help us understand the use case more. We have no problem adding new features to JFBConnect, or even providing you with some simple code that would only publish 'public' content instead of 'public' and 'registered'. We do like to make sure we understand the use case so that we aren't adding features and checkboxes that help only a limited set of users and confuse the rest though.
Today I go into the Facebook Social Channels to start fooling with the settings, in a last ditch effort before giving up, and there is a new drop-down that is Autopost Access, which shows my access levels.
I'm unsure where you're seeing this setting. Can you explain further?
We don't have a method to directly select which access levels for an article are published. However, there are some built-in checks and configuration options you may be able to make use of:
* Articles marked as special are never automatically published
* Articles marked as registered are published and the link and intro text will be included. If a user clicks those articles in a social feed, they will be brought to your site and asked to login. This is a good way to get users to your site with 'teaser' links and works well on many sites.
* Autoposting can be setup on a category basis. If you have a section of public content in one category and you post authenticated content in a separate category, you can easily set the authenticated category to not auto-publish.
I hope that gives you some ideas, but if you have questions on how best to do what you're looking for let us know. If the above doesn't give you the flexibility you need, help explain further and we can investigate changes for a future update.
We're making your life fun aren't we?
The 2000 fans thing was introduced last year. Originally, it was like 100 fans and they keep increasing it to the now-current 2000. We weren't even aware of this change until about 6 months after it was first announced as it was pretty buried, but you're right, we should make it more clear.. and fix Autotune to not require a Page Tab. When Page Tabs were originally added, they were a very popular feature and setting one up had no ill-consequences if you didn't use it. Since then, app reviews, minimum fan requirements and a whole host of other changes have occurred. I've added it to our task manager to allow blank / disabled settings for those fields.
To remove the Page Tab feature from your application, you'll need to do it in the Facebook Developer Area:
* Click into your app
* Go to Settings -> Basic
* Scroll down to the Page Tab section and click the 'x' in the top right corner of that section
Don't run autotune again while you're submitting your app for review.
I hope that helps and sorry for the confusion.
It looks like they are requiring all apps to go through review for manage_pages now. If you use the Channels feature of JFBConnect, you'll need to go through the review process.
In general, that entails letting them know that you (the admin) are adding content to your Page from your website. You don't add content to general users Pages or pull in feeds from other Pages, just the ones you manage. Pictures of the JFBConnect admin area and/or a stream view of your page on the front end (if you use that feature) is suggested.
You can read more in our blog post Facebook's App Review Process Explained.
I hope that helps,
A Page Tab App is when you add your site (through your Facebook Application) to a Facebook Page. The result is like:
https://www.facebook.com/SourceCoast/ap … 908376294/
It's our home page showing inside our Facebook Page. You can use that feature to show a specific page of your site, like a support section, a newsletter signup form, a coupon for Facebook visitors, etc. You can set the URL in the Facebook App configuration for Page Tab URL (either through Autotune or in the FB Developer Area).
To add it to your Page, you can go to the Page Tab/Canvas area of JFBConnect and in the "App as Page Tab" section, there's a line like:
Your Page Tab application appears to be setup properly. To add it to your Facebook Page, Click Here.
Use that link to add your Page Tab to your Page.
With all that description out of the way, I haven't heard of FB requiring you add a Page Tab to your Page when requesting a new permission. What permissions/scope are you requiring? If you don't want the Page Tab you may want to remove the URLs for Page Tab URLs and re-submit. They may be thinking you want to use that feature and want to see an example first.
I hope that helps!
There's 2 separate issues you seem to be mentioning here. One is easy to correct, the other isn't as easy.
Can't load url: the domain of this url isn't included in the app's domains.
To fix this, please go to the Facebook Developer Area. Click into your app and go to Settings -> Basic. In there is a field for "App Domains". Add any domains you use for your site, which I would assume would just be:
Now, for the other issue in your quoted message from Facebook, it seems they have marked your app as a 'negative user experience'. That can happen for many reasons, including sharing content that others have considered offensive, 'fake news' type sites or anything else that may have caused users to report your site. In looking at your site, I don't see anything that would indicate this, so I'm not sure how you earned that negative view. You may want to submit an appeal and explain your sites purpose and how you interact on Facebook. It seems strange that your app was restricted from my perspective, but you know your site and content better than I do from a quick glance.
I hope the above helps,
I hate to tell you, but deleting and recreating usually doesn't help move you up the queue. I hope that works out for you though.
If you switch out the Application ID, please also make sure you:
* Delete any mappings in the 'User Map' area for Facebook. Those mappings are app-specific, so you can run into issues if you change the App ID
* Delete any channels you created using the previous app.
* In the Autotune section, make sure you hit the 'Refresh' button in the menu area of the FB App section.
I hope that helps, but if you continue having issues, let me know.