RESOLVED: JFBC system plugin causing 404 error with AMP pages

Sorry I missed this before. I have no idea why you'd be getting a 404 error with the JFBCSystem plugin enabled. I don't know how AMP rendering is being done within jReviews, but it shouldn't cause our extension to behave differently or redirect the user to an incorrect page, obviously.

Can you tell me if the URL is the same when the JFBCSystem plugin is enabled vs disabled? Knowing if it changes can help narrow some things down. We'll probably need FTP access to your site to investigate where things are going south though. If you can send that and super admin credentials to us by PM, that'd be great.

Thanks,
Alex

Sorry for the delay. I just responded by PM to give you my IP address to investigate further. However, I'm very confused by the following:If the JFBC system plugin is disabled and it still fails, I don't think this is related to JFBConnect. Can you explain more about the setup and how you're testing including when it works and when it doesn't?

Any details will help us investigate a helluva lot faster.

Thanks,
Alex

Mark,
Whew... thank you for patience. I did a bit of investigation tonight and was able to get things going. Fortunately, there weren't any code changes necessary, just some shuffling and configuration settings to do it. Here's what I did:
* I moved the JFBCSystem plugin *after* the wbAMP plugin. This got rid of the 404 error because the /amp at the end of the URL was causing some problems for our parsing of the URL.
* After this, the page loaded, but a bunch of JFBConnect Easy-Tags showed on the page, like {JFBCFacebookLike ...}. It was ugly. In the wbAMP plugin, there's an option to disable specific content plugins from loading in the 'Cleanup' section. I used that area to disable the JFBConnect - Content plugin on AMP pages

With that, voila! All seems good! Please test and let me know how it goes, but the changes seemed pretty benign, so hopefully it's smooth sailing from here.

Thanks,
Alex