artifexmedia

@postnl Thanks, I know enough

@geminilabs All reviews are litteraly in the “Rejected” state, so they appear red in the dashboard, with a red border and it has a status Rejected. I cannot post an image here, sorry

Maybe that’s the way it work’s but in my opinion the administrator of website in this case will never know which review he has rejected himself and which review the system has auto-rejected for approval.

I checked your screenshot, I do not have the blacklist option enabled, so that does not seem to be the issue and I do require approval – but when I set to No: it does not auto-reject. (A better way. in my opionion, would either be a new status or to use the “Private” state or Concept mode or something else (but, that’s my opionion).

Nonetheless it’s a really great plug-in though :)!

@geminilabs The translation is a bit off because in Dutch it looks like it wants to say the name of whoever posted the review, as it’s says “van” and “van” litteraly means “from”, not “of”. Suggestion to change that to “on page”, to clear that up ??

In that case, [PAGE_TITLE] is not working. We used the shortcode without assigned posts, we just applied the shortcode below on an Elementor page “Post review”:
[site_reviews_form]

However, when posting a review, you get above e-mail without the [PAGE_TITLE] injected, it’s just empty as explained then.

I am/was expecting it to auto-detect the post/page ID as that is fairly easy to do with WP – or, if that is not the case with this shortcode, maybe you can change the e-mail subject to do some other subject like: “4-star review posted”, without the “from/of” (maybe that is the issue – the [PAGE_TITLE] is not even there and just the from/of just has to be removed yet?)

@postnl Still no reply, the page still says “As soon as more information is available, this will be shown here.” and it’s 15-12-2021? The deadline is near?

Hey @kovshenin

Thanks, will look into that!

Indeed this website, which as an old bought theme uses some session_start() function, I’m using this old website as an test location for Surge and good to know that this is being a blocker. I’ll switch to another test website shortly and I’ll move to my own post now which I just made also ??

@kovshenin I should be starting a new post but since this is a WP Rocket thread I want to ask here, also for the one who asked.

I am using WP Rocket and I used the addon you suggested @fredericlegrand, however it seems now my pages are static html pages from WP Rocket and not Surge.

How can I confirm the pages I am seeing are from Surge and not WP Rocket’s static pages?

I need to clarify: Surge does not minify, compress JS/CSS, etc, but WP Rocket does.
I want to combine Surge and WP Rocket for Surge’s functions and WP Rocket’s functions – as you mention you can combine them.

Example url: texelinbeeld.nl (see source code, last line – shows WP Rocket)

Hey @wfpeter,

Lifesaver, thanks!
Is there any reason the redirect goes wrong though? Can we possibly get a fix for that or is it not possible?

@squilib Thanks for your input!

Plugin builders do not respond to tickets, email or deliver support at all…

Hi @niklasinpsyde

The e-mail is already sent out correctly, I just received a confirmation that it has been received.

However, I will reply with a status report now.
Thanks in advance

Hi there,

Thank you! Forgot to let you know we updated.
However, Instagram has introduced a strict origin when cross origin policy, meaning the public feeds cannot be fetched anymore and API is needed from now on

Could you confirm this?

Hey @5um17 ,

Thanks, that indeed solved the issue.
Do you have an estimate of when the plug-in’s new version with this fix will be released, so I can put back the original one?

Thanks for the fast reply!

Hi,

Thank you, could you let me know when it’s estimated to be released?

Hi,

There are no JS errors ??

Hi,

Thank you for the info, however – no luck.
I did in fact already had the plugin installed and used all of those buttons before as well, but tried it again; no luck – same error ??

Same issue here on 3.1.1