Facebook Login and Facebook Page Sync for Osclass
Facebook Login authenticates users; Facebook Sync publishes listings. They solve different Osclass problems and should be configured separately.
Two different Facebook integrations
Facebook Login and Facebook Page synchronization are often grouped together, but they solve different problems. Login is an identity feature: it helps a visitor access or create an Osclass account. Page synchronization is a publishing feature: it sends marketplace listing content from Osclass to a Facebook Page.
- Use Facebook Login when the goal is easier user authentication.
- Use Facebook Sync when the goal is listing distribution and Page activity.
- Use both only when both business goals are useful to the site.
Plan Facebook Login as an authentication channel
A Facebook login integration needs a Facebook application, the correct redirect/callback settings and server-side handling of the returned identity. The site should keep normal Osclass Login available so account access does not depend on one external provider.
- Match the redirect URI exactly.
- Request only the permissions the login flow actually needs.
- Handle existing email addresses carefully to avoid accidental duplicate accounts.
Plan Page synchronization as a publishing workflow
Listing synchronization needs a Facebook Page connection and a controlled rule for what gets published. A marketplace should not post every edit blindly. Decide which listing states qualify, what text and link are included, and what happens when a listing is changed or removed.
- Keep Page publishing separate from user authentication credentials.
- Use listing URLs that point back to the canonical Osclass listing page.
- Avoid duplicate or repetitive posts that add no value to followers.
Relevant TTB products
TTB Facebook Login handles the Osclass authentication use case, while TTB Facebook Sync handles marketplace-to-Facebook Page publishing. Keeping them as separate plugins makes the permission model and troubleshooting much clearer.