frosy

Hi Alex,

It requires lots of CSS tweaking in OptmizePress to get that ability as our pages have containers and padding set on the rows.

We have rolled out our own image slider as part of our PlusPack. You can see it here: https://optimizepress.zendesk.com/hc/en-us/articles/226479448-How-to-use-the-PlusPack-Image-Slider-element

It’s not a feature rich as Meta but you can scale it to full width.

Hope that helps.

David

If you have any questions regarding OptimizePress try https://help.optimizepress.com we’ll happily help out if we can.

@mentalist2009 Did you hear back from support?

Were you able to get your site restored at the host?

Exactly right!

Most people end up using a crappy hosts because some marketing guru recommend a host where they get paid $60 affiliate commission per signup.

Get yourself a decent hosting account.

We fixed this our end.

Check your PHP fpm.log file and see what errors show, like:
WARNING: [pool www] server reached max_children setting (4)

Basically the php processes were maxing out so we bumped up the PHP to allow 8 processes at 256MB.

I’m lost on this.

I’ve disabled all plugins and changed themes and still the product admin is soooo slow.

I have 128MB of memory set in PHP, the server has 1GM of memory, the site has 316 products.

The server uses Varnish caching which I’m going to troubleshoot next but I can’t see how varnish caching would cause this issue. The site is super fast everywhere else. I’ve fined tuned my front end to be a quick as Shopify but the admin is killing us.

Next option is moving to Shopify so we can manage products quicker.

Anyone found a fix for this yet?

Woo says there’s no issues with there test (they should actually try a live site and not a demo install with 5 products and no data).

Hi All,

We are coded a solution for OptimizeMember which has worked.

Please open a support ticket and we’ll update you. For those of you who have open tickets we will reply with info.

Best regards
David

Hi Yurry,

I replied to you with some info. Hope that helps.

Best regards
David

We are still testing some alternative solutions to get Paypal working.

Please content OptimizePress support and our team will happily help you out.

Best regards
David

Hi All.

I work with OptimizePress and we have been extensively troubleshooting this overnight with our hosts, customers hosts, servers running SSL’s etc.

It’s not an issues related to OptimizeMember or OptimizePress.

It appears to be SSL related with the host (at server level and IPN). Paypal may have rolled out recent changes earlier than planned on the signing algorithm of certificates (from SHA-1 to SHA-256).

We are seeing the issue on numerous sites and also s2Member sites we have tested.

If any OptimizePress customers have questions please contact our support team, we’ll be happy to help and provide alternative solution to test.

Best regards
David

Hi Chris,

Try creating a new membership button in OPM and see if that works.

Did you say it worked fine before?

David

By the way you might want to check which email is sending to Aweber.

They have recently update their rules to not allow role-based email to parser data.

EG if you are using webmaster@ info@ admin@ the parser may not work.

Yep I’ve reviewed his post.

“you really can’t switch back to visual” that’s not practical.

We all switch between view to see what’s being coded.

Even if I don’t switch between views and add 100 line breaks between paragraphs WordPress decide to remove those paragraph tags and make only 1, go figure…….

I’ll use the advanced editor until the bug is fixed.

Thanks for taking the time to reply. This should be on the “known issues” list, save people posting again and again.

Thanks t-p

I also update yesterday on a defualt site, default theme default everything. Just good old WordPress, nothing else.

When I edit a page in hmtl add <p> then switch to visual and back to html it removes the <p> tag.

TinyMCE doesn’t do this on other sites I’ve used (not WP sites). So the bug is within WP which everyone is aware of. I was just seeing if it had been fixed in V3.0