NEdwards
Forum Replies Created
-
Thanks Justin (@slickremix),
It certainly makes more sense to me that it’s a bug and not something done on purpose. It seemed super weird to disallow pulling the profile photo but to completely allow pulling all the page’s posts.
Anyhow, is there anywhere public where that bug is being tracked? Would be nice to be able to periodically check on that without having to hit you guys up. Hopefully a fix implemented on Facebook’s side wouldn’t necessitate an update to your plugin, but you guys seem pretty responsive so that’s good.
I’ll try and see if my client is okay with turning off the restrictions or hiding the profile photo temporarily. Hopefully that bug is fixed soon.
Keep me posted, thanks!
Hey @slickremix,
Thanks for the prompt reply.
Are you saying it is impossible to pull profile photos for pages that have these restrictions? Are there any alternatives or workarounds? Do you know if it can be done by writing custom code instead of utilizing your plugin?
Any help is appreciated.
Hi @slickremix,
I’m also experiencing this issue.
Would have been super nice if you had posted the solution here publicly. Do you have that handy?
I’ve already done a bit of research and determined that sometimes this can be caused by permissions issues, with the Facebook page being set to 21+ only. Unfortunately for me, I cannot just change that, as I am trying to pull posts from a page for an alcoholic beverage distributor. The page must remain 21+.
Any help is appreciated.
I have also encountered this same issue with a theme called Newspaper (version 8), by tagDiv.
I am unable to use the additional options that theme adds to the menu item options because it appears that Ultimate Member is completely overriding them.
I am using the latest release 1.3.88 and this is still broken.
Forum: Plugins
In reply to: [SEO Ultimate] creating huge files in php error logI just wanted to post here to bring some attention to this issue.
It appears as though a site I’ve been working with experiences this as well. Each line of the PHP error_log is about 1mb… this adds up quick.
I figure it is probably resulting from one specific URL that is 404ing, but has had 25546 hits. The url in question is a JS file linked in the head of the theme, so it logs a hit every time a page loads anywhere on the site.
The data that the 404 plugin is trying to log to the database is probably inflated as a result of the numerous hits. Corey, if you actually check your 404 log page, are there any particular URLs that have had a significantly larger number of hits on them? This is just speculation, but I’m looking for situations that most people won’t encounter, since it appears not many people are having this issue.
In the meantime, I’ll be resolving that specific URL (and leaving the 404 monitor turned on) to see if this will resolve the issue.