Prometheus Fire

Got it, this is very helpful and points me in the right direction.

Thank you for the information!

You can disregard this. I broke this myself by removing a custom taxonomy that the loop I had created was dependant on.

Thanks!

Yeah, I see what you mean. I tried a few things and couldn’t find a solution.

The interesting thing was that it reverted back to the right position in most browser/OS combinations. Unless another way can be found we may have to live with it.

Since it usually went back to the correct position in most cases, I darkened the opacity of the overlay to 95% to make the jump less obvious. The only computer it didn’t jump back to the position on the page was on my Ubuntu computer and I might be the only user of the site who uses Ubuntu…..

Maybe the solution for now is to hide in by darkening the overlay. You might consider that in the next update.

I don’t think this is solved yet. I’m experiencing the jumping problem on a site I am working on. Loading the popup causes the page beneath to jump to the top. When the popup is closed it reverts back to the correct location on the page. Correction to that, it does not revert reliably. I did a bunch of cross-browser testing using Browserstack that it does revert in Windows IE, Mac Safari, and Mac Chrome. I found that it did not revert properly in Ubuntu Chrome.

However, if we can get the jump prevented in the first place, it would be less jarring.

Unfortunately, the site I am seeing this on is a restricted access site so I can’t give access but can confirm that in the current version (2.1.11) the issue is still present.

• This reply was modified 6 years, 4 months ago by Prometheus Fire.

Found it. That was the Expand Details option. I didn’t understand what that was for at first. Thank you!

Previous version can be downloaded from this page. Just deleted the current installation and install like a normal plugin. You may need to reset your settings.

https://www.ads-software.com/plugins/restricted-site-access/advanced/

Can report the same issue. The logged-out user redirect happens even when logged in.

Am able to access the dashboard, but not the front of the site as it just keeps redirecting. Reverting back to 6.1.0 for now.

I think I’ve found a solution.

I added a little bit of padding to the top of the div your plugin creates

a.bsptopic {
  padding-top: 100px;
  display: inline-block;
}

That gives a better jump to the form. While it does have a whitespace on the page, it isn’t that awkward. I’m marking this as resolved, but I’ll leave that link valid for a week or two for you review if you like.

Yeah, sorry about that. The site owner deleted the group I was using for that.

I created another one for you to look at https://classroom.wowwritingworkshop.com/workspaces/test-group/

The URL has been updated. That one is no longer any good.

https://classroom.wowwritingworkshop.com/workspaces/college-essay-institute-seminar-002/forum/

https://104.131.77.12/workspaces/college-essay-institute-seminar-002/forum/

It is a site in development and everything is meant to be locked down later on. However, I’ve made that BP group and forum public and set the forums to allow for anonymous posting. It uses a different form for anon posting, but I think you can still see the scrolling issue

I appreciate the quick reply. That was very nice of you.

The client wanted to try something else, though we may revisit this in the future. I’m marking this as resolved for now so you can keep your support topics under control.

Thanks!

Nevermind…this was user error.

There does seem to have been a change in how things are handled with the open URLs though. In my list of open URLs I had the root domain listed to ensure that the homepage would be displayed. The presence of the root domain seemed to make all the pages on the site available. Once I removed it, the protections starting working again.

ANyhow, this is resolved. Sorry for the inconvenience!

I started getting this error recently with this plugin, which is strange because it was working fine before.

Did you solve this?

So, after some further testing, I can say that Sell Media is not compatible with PHP 7.1. I downgraded my PHP version to 7.0 and the error in the source code went away, and I can confirm that the other PHP warnings were no longer logging into the debug log.

So, overall not a huge issue then at this point. 7.1 is pretty bleeding-edge so it isn’t a problem yet really. Probably something worth noting and taking a look at in the not to distant future!

Thanks.