ConjurerGFX

Hi,

I got the same problem but I have solved it. Looking at this page (https://stackoverflow.com/questions/23921891/the-soundcloud-wordpress-plugin-generates-mixed-content-errors-when-viewing-page) I came up with the following modification.

Added a trailing slash after https://w.soundcloud.com/player. Line number 170 of file soundcloud-shortcode.php (folder wp-content/plugins/soundcloud-shortcode)

function soundcloud_iframe_widget($options) {

  // Build URL
  $url = 'https://w.soundcloud.com/player/?' . http_build_query($options['params']);

I hope this helps others!

Ok thanks for your reply.

Hi Vladimir,

Can you please confirm whether I have to use 0 or 7 for Sunday?

Besides that, I have found that using 20:00-0:00 does not work. Changing it to 20:00-23:59 does work. Is this a bug?

Kind regards,
Paul.

Thank you!

Kind regards,
Paul.

Hello Vladimir,

Thank you for your response.

According to the documentation in the scheduler option window sunday is identified by days_week="0":

“Days of the week

In this field you can specify one or more days of the week. Every week at these days the content of shortcode will be visible.

0 – Sunday
1 – Monday
2 – Tuesday
3 – Wednesday
4 – Thursday
5 – Friday
6 – Saturday“

I will try your suggestion but is the documentation incorrect?

Kind regards,
Paul.

@mbrsolution, thank you for your support!

@wpsolutions:
Thank you for your reply. I will disable the whitelist and wait for a fix for this plugin.

King regards,
Paul.

I do not have an other security plugin installed. All in one WP security and firewall is all I have installed for security purposes.

I do use the W3 Total Cache plugin. It’s not a security plugin but it does make some changes for rewrites etc.

Thank you for your reply.

What I have tested is the following:

Test scenario #1

Situation:
Option rename login page enabled.
Option login whitelist enabled (IP address from another location with different IP address not in the list).

Scenario:
Trying to login from another location with a different IP address on the renamed login page.

Outcome:
Getting the WordPress login screen.

Test scenario #2

Situation:
Option rename login page disabled.
Option login whitelist enabled (IP address from another location with different IP address not in the list).

Scenario:
Trying to login from another location with a different IP address on default login url like so: https://www.mywebsite.com/admin

Outcome:
Getting a non-Wordpress credential login screen with title “Connect to <website>”.

Hi mbrsolution,

Thank you for your answer. Sure I can.

When I have renamed the login page to for example ‘my-alternative-login’ I have to login using the url ‘www.mywebsite.com/my-alternative-login’. So far so good, this is working nicely.

Then I have input my IP address (for example 1.2.3.4) in the whitelist and I enabled the login whitelist functionality. Next I logout and try to login again in using the URL ‘www.mywebsite.com/my-alternative-login’. This is also working as expected as my IP address is in the whitelist.

Next I try to login from an other location with a different IP address (for example 4.3.2.1). This IP address is not in the login whitelist. Trying to login to ‘www.mywebsite.com/my-alternative-login’ succeeds, I see the login page and can input login credentials. This is not as expected. What I would expect is that I would be blocked (displaying an error message), redirected or such.

Kind regards,
Paul.