Robert

Hi @danieldumitruavram

Please note that we are unable to provide support for custom coding of any kind.
Currently, your code will return the unchanged notification email in our case, as the condition you set will be evaluated to true.

If you cannot seem to make this happen, then I would rather recommend getting the Pro version, or hire a developer who can make the code for you.

Hi @confusedneedhelp

Sure, I restored it now, so you should be able to access it again on the original link:
https://www.dropbox.com/scl/fi/qjpvap6mo00r4wftwuavz/nextend-social-login-feature-NSLDEV-649-bfcache-cannot-work-because-of-broadcastchannel.zip?rlkey=mggie9mk6tevzx7896tlomjtg&st=h9sl5eip&dl=1

Hi @dragansk!

Thanks for contacting us!

I’m sorry, but in WebView browsers we hide the Google button on purpose, as Google doesn’t allow using their OAuth endpoints over WebView, since according to them that is not secure ( https://auth0.com/blog/google-blocks-oauth-requests-from-embedded-browsers/ ).

This means whenever a user tries to connect with Google while they are browsing over WebView, they would only see an error message that states this problem. So because it cannot work, we are hiding the Google button on WebView browsers by default. However, since Nextend Social Login 3.1.12, we have a new option – Unsupported WebView Behavior:
https://nextendweb.com/nextend-social-login-docs/global-settings/#unsupported-webview-behavior
With this option you can either remove the buttons (default behavior), or you can disable them (in this case the buttons will still show up, but will be grayed out), and if the user still clicks on the button it will show an error notice stating this limitation.

If you have any questions, let me know!

Hi @tmora

The entire error message is rather strange. It refers to a function called shmop_delete:
https://www.php.net/manual/en/function.shmop-delete.php
We do not use this in our code, or any low level memory management function for that matter, so our code might have been modified somehow on your website. First, please check this file:

• wp-content/plugins/nextend-facebook-connect/includes/oauth2.php

And go to line 220. You should see this:

        if (function_exists('random_bytes')) {
            return $this->bytesToString(random_bytes(self::CSRF_LENGTH));
        }

Do you see the same code part as above? According to your error message it looks like random_bytes might have been replaced by this shmop_delete funciton.

If that is the case, please delete your current Nextend Social Login installation, and install it again. Your plugin settings will stay, so don’t worry about those.

If the problem still appears afterwards, then if you make a test php file (e.g. test.php) with this code:

<?php
var_dump(random_bytes(32));

And open this test file in your browser, do you see the problem there? And also please check this code as well:

<?php
var_dump(substr(bin2hex(random_bytes(32)), 0, 32));

If you see the error still, then we suspect that somehow the random_bytes function is incorrectly configured, or an issue similar to it.

Hi @tmora

Officially PHP 8.4 isn’t yet available, so it is totally possible the issue stems from a core PHP issue, which might get resolved once the version is officially available to everyone. Either way, please let us know exactly what error message you see, so what exact critical error message you get (currently only the trace of the problem is visible, so not the exact issue). If it wouldn’t be written out, you could ask your host, and they should have a log about these issues, which should contain the exact error. Let us know, and we’ll take a look at this.

Hi @confusedneedhelp

I am not that familiar with bfcache, but according to the notice you see, the problem is that this caching cannot happen because there was a BroadcastChannel instance with listeners registered. We use this BroadcastChannel to keep the connection between the opener window, and the opened window whenever the opener window data is not available. This is important, because otherwise after the authentication and authorization with the provider, the popup would not close, and instead the login and redirect would happen there, so with this BroadcastChannel we can keep the information between the opener and opened window and close the popup and redirect in the opener window, as you would expect.

For now I have updated our code, and with the modification the problem no longer occurred. You can download it from here:
https://www.dropbox.com/scl/fi/qjpvap6mo00r4wftwuavz/nextend-social-login-feature-NSLDEV-649-bfcache-cannot-work-because-of-broadcastchannel.zip?rlkey=mggie9mk6tevzx7896tlomjtg&st=089gqipf&dl=1
To install this, make sure to delete your previous version of Nextend Social Login (your plugin settings won’t be affected), and then install the one above:
https://nextendweb.com/nextend-social-login-docs/installation-guide/

Currently our senior developer who reviews code changes is out of the office, and won’t be available till Friday, but if everything works fine for you, then we will review the code, and add it to future releases.

Hi @jltest

I assume you used the File/Image/Video field type. The problem with this is that this will not return the actual URL of the image, but rather the attachment ID. Unfortunately, we don’t have code specifically for Pods, so we just retrieve the meta data of a post as it is stored, but we can’t go any further than that. So the problem here is that the URL of the image itself has no direct connection to the post, but if you could somehow solve it, for example with a custom plugin or custom code, so that the URL is also saved as meta data, then it could work. Or if it would be possible, you could use the Advanced Custom Fields plugin, which we wrote direct code for the Image field to retrieve the image based on the ID.

If you insist on using Pods, you could get the images as URLs with custom code. Please note we have no support for custom coding, nor for any problems or questions related to custom coding. We have a “smartslider3_posts_customposts_data” filter that allows you to add custom fields in the custom posts generator. You could use this to convert the attachment ID to an URL. This is an extremely basic solution for that:

function custom_smartslider3_posts_posts_data($record) {
     $record['image_url'] = wp_get_attachment_image_url($record['hotelimage'], 'full');
     return $record;
}

add_filter('smartslider3_posts_customposts_data', 'custom_smartslider3_posts_posts_data');

Here the field ‘hotelimage’ contains the attachment ID, you will need to use your own field name for that.
And the image URL would be in the “image_url” variable, so that is what you would insert as the background in the slide.
Also, like I said, this is a basic solution, and it doesn’t consider other factors, which could cause problems, and you may need to extend on this code to fit your needs, but like I mentioned above, we are unable to help with custom coding, so if you do not want to bother with this, I would rather recommend using the Advanced Custom Fields plugin.

Hi @nicolbc

We don’t have an option to set percentages for the sizes, and you should think of the slider sizes as more of an aspect ratio than a fixed size, so on smaller screens it will be smaller, on bigger screens it will be bigger by default, but you could also use the “Boxed” layout:
https://smartslider.helpscoutdocs.com/article/1775-boxed-layout
This makes the slider occupy the area of the container you put the slider in. Then you could change this container as you see it fit, and the slider will cover that area.

As for the image:
It’s based on the “Slide background image fill” option:
https://smartslider.helpscoutdocs.com/article/1809-slider-settings-slides
how your images look like in the slider. By default the “fill” option is used which will make the image as big as it needs to be to cover the whole slider. This means that if the slider and image ratios differ, the image will be cropped. To avoid this behavior you could change the fill mode to “fit” or “blur fit” instead.