pikamander2

Hey @craig-at-smash-balloon , I’d prefer to do it server-side if possible so that it appears correctly at the very start and doesn’t have to wait for the JavaScript to load.

I could probably edit the plugin directly, but then it would break when the plugin gets updated.

Would it be possible for you guys to add an option or hook?

Good eye. I wasn’t the one who wrote it, but I should have caught that.

• This reply was modified 6 years, 5 months ago by pikamander2.

@icegram – Looks like this issue still exists:

[Tue Oct 16 17:03:11.489048 2018] [proxy_fcgi:error] [pid 17725] [client 127.0.0.1:42266] AH01071: Got error 'PHP message: PHP Warning: Illegal string offset 'es_registered' in (my site)/public_html/wp-content/plugins/email-subscribers/classes/es-register.php on line 1188\n', referer: (my site)

The function in question is function es_sync_registereduser and the problematic line is:

if ( ( $es_sync_unserialized_data['es_registered'] == "YES" ) && ( $user_id != "" ) )

A quick fix would be:

if ( (isset($es_sync_unserialized_data['es_registered']) && $es_sync_unserialized_data['es_registered'] == "YES" ) && ( $user_id != "" ) )

But you may also want to look into why it wasn’t set to begin with.

• This reply was modified 6 years, 5 months ago by pikamander2.

Nevermind, looks I just had to reupload the images or regenerate their thumbnails.

@nko – Thanks, that fixed it.

This is happening to us as well. I can’t find much about it but somehow Limit Login Attempts is blocking localhost (127.0.0.1) instead of the attackers’ IP addresses. The result is that whenever someone enters bad credentials, everyone gets kicked out of their account and nobody can log in until the ban expires.

Are you by chance using Cloudflare or WebARX? I’m wondering if it could be some kind of conflict.

Edit: According to this thread, it may be a conflict with Cloudflare. I can’t find any good documentation about this though. Is there a way to fix this?

Edit 2: I did some testing and it seems that you can whitelist 127.0.0.1 to prevent the lockouts, but that also prevents legitimate lockouts as well.

• This reply was modified 6 years, 7 months ago by pikamander2.
• This reply was modified 6 years, 7 months ago by pikamander2.

@nko – All I really need is to be able to put a custom anchor tag link around each portfolio.

But when I try this:

<a href="https://example.com">[visual_portfolio id="2291"]</a>

It appears to output the visual portfolio completely outside of the anchor tag.

Any idea how I would fix that?

• This reply was modified 6 years, 7 months ago by pikamander2.

That’s surprising. From what I understand, it’s not possible to make a continuous slider like this without being able to remove the easing.

Would it be possible to add a checkbox for that? Even in normal sliders it seems like it would be a useful option to have.

Hi Mark, thanks for the help!

That rule does seem to fix the “element-is-not-sticky” problem, however it also seems to cause two new issues:

1. The header now stutters a bit when you first scroll down.

2. Because the sticky header has 1px less of top margin than the not-sticky header, the contents of the header shift by 1px when the change occurs.

I was able to fix the second problem by changing the rule to:

#masthead {
   margin-top: .1px;
}

However the first issue still occurs. It’s awfully jarring compared to how smooth the sticky header normally is. Is there any way to get rid of that?

The error message is:

Only .mp4 or .mov files may be used for header video. Please convert your video file and try again, or, upload your video to YouTube and link it with the option below.

The validation is being done by _validate_header_video:

The reasoning, according to the comment in that function, is that MP4 and MOV are the only cross-browser-supported formats. While it’s true that they have greater support, the majority of users can currently view WebM videos as well. If nothing else, they should be allowed with a warning.