marscom

I am most probably too stupid: When I delete the account and add it from scratch, I’m asked to reconnect my personal Insta account again (that’s not what I want on my customer’s sites…). Even if I do so, just to try, I get the message “Du bist leider nicht berechtigt, auf diese Seite zuzugreifen” (not authorised to acess this page).

I generally do not like tinkering and work-arounds on extensions. I prefer them to work as they should. So … I’ll wait until Mr. Zukkerberg approves your request.

Thanks anyway

Martin

Hi,

thanks so far! I have three sites which use the SFG. The Insta users are:
glthaldimann
lenggerspilluet
hurnifiechter

Thank you!
Martin

Dear devs,

I really, really appreciate your work and I think you are seriously interested to solve this issue. But: our sites still show this ugly “Error 400” alert and we would be grateful to get some info about the proceeding. Just to know you care and that a fix is on the way. And … what is the timeline until the plugin works again.

Thanks,
Martin

Are you still working on this issue? Would be great to get some news, just to inform my customers about what’s happening.

Thanks!
Martin

Not working on personal accounts. See here:
https://lengger-spil-luet.ch
https://glt-haldimann.ch

Error: 400: Bad Request

• This reply was modified 10 months, 1 week ago by marscom.

Well, thanks. But this is not exactly what I had in mind. Is it not possible that the customer can export the .csv without having to rearrange the columns every time?

Hi,
got probably the same issue. Until recently, the Insta feed worked flawlessly. Suddenly, the 400-error in the frontend. I deleted the existing account and tried to connect at new. This is what I get:
“Entwickler-Rolle nicht ausreichend: Entwickler-Rolle nicht ausreichend”
Meanwhile, I deactivated the plugin and installed another one. But I’d love to keep the quadlayers …
The site in question: https://lengger-spil-luet.ch
The insta account in question: lenggerspilluet

Martin

Hi Jarnovos,

Thanks for taking care of this issue! Yes, this is the plugin I have in use. Meanwhile I spent some more – more time fumbling around in the Complianz settings. Somewhere I deactivated the WP Store Locator – and now it works. But of course, the plugin loads even if I do not accept the cookie settings…

But to be honest: In Switzerland, this is not really a big issue. Would be kind of different if the shop would target customers in the EU.

So for now, instead of spending even more time with finding out how to tweak Complianz in order to work with WP Store Locator, I leave it as it is…

Martin

File permissions are absolutely standard. The site is online since at least 10 years and is on the same hosting platform as all of my other customer’s sites ??

Sorry, still fatal error, this time on line 20:


Warning: require_once(/var/www/vhosts/dreyer-ag.ch/httpdocs/wp-content/plugins/simple-masonry-layout/includes/class.simple.masonry.admin.php): Failed to open stream: No such file or directory in /var/www/vhosts/dreyer-ag.ch/httpdocs/wp-content/plugins/simple-masonry-layout/simple-masonry-layout.php on line 20

Fatal error: Uncaught Error: Failed opening required ‘/var/www/vhosts/dreyer-ag.ch/httpdocs/wp-content/plugins/simple-masonry-layout/includes/class.simple.masonry.admin.php’ (include_path=’.:/opt/plesk/php/8.0/share/pear’) in /var/www/vhosts/dreyer-ag.ch/httpdocs/wp-content/plugins/simple-masonry-layout/simple-masonry-layout.php:20 Stack trace: #0 /var/www/vhosts/dreyer-ag.ch/httpdocs/wp-admin/includes/plugin.php(2318): include_once() #1 /var/www/vhosts/dreyer-ag.ch/httpdocs/wp-admin/plugins.php(192): plugin_sandbox_scrape() #2 {main} thrown in /var/www/vhosts/dreyer-ag.ch/httpdocs/wp-content/plugins/simple-masonry-layout/simple-masonry-layout.php on line 20

Thanks for your friendly, quick and really helpful support! I’ll give that a try. But for today, I still have to digest this morning’s shock moments ??

Martin

Same here. Fatal error, site down. When deactivating Gwolle, no issues at all.

Already did the standard check: isolating/deactivating all plugins and re-activating one by one. Together with my hosting provider we found … that it’s indeed just the TTfP. As mentioned by the second poster, I can confirm that the plugin wants to consume an impossible hight memory.

B.t.w: One cannot uncheck the functions according to your screenshot, as … the backend is not accessible when TTfP is active ;-).

• This reply was modified 2 years, 4 months ago by marscom.

PHP 8.0

Same here! Blank screen after login. Isolating the plugin helps.
Memory size was 1GB – and still not enough…