jaschaio

Any size should work. Please note that there was a small bug causing the logo to display badly. We just issued an update that should resolve the problem.

Sure,
you have three background options. You can find them all in the styling section within the plugin options panel.

The first one is the one you already mentioned, is the “Box Background”.

It is responsible for the inital white box.

The next “layer” is the “Background Overlay Color”.

It is a layer that lies between your background image and the white box. It is usually set to a transparency of 20% and a dark black color. You can set this to a solid color (no transparency) or set to a 100% transparency to make it invisible.

And the third, and last background layer is the “Page Background”.

People usually upload a background image, but you can click on the red “Remove” Button and choose to show a solid color instead by clicking on the “Select Color” Button.

This will automatically make the “Background Overlay” invisible.

I hope this answered your questions. If you need any more help feel free to write to support [at] growtheme [dot] com at anytime.

• This reply was modified 8 years, 2 months ago by jaschaio.

Hey Jeff,
I got your email and we already were able to resolve this problem. The Coming Soon Page didn’t displayed because it still wasn’t enabled within the plugin settings.

For reference this is how the plugin settings should look like:

Thanks and best regards

OS is Ubuntu 14.04

How can I find out if it uses LOG_AUTHPRIV?

I will put that into my wp-config anyway and see if it helps.

Hey Julian,
can you write me the URL of your landingpage to support [at] growtheme [dot] com?

What do you mean with use of fields? Do you mean the use of Mailchimp Merge Fields?

I am currently working on the documentation and I will inform you as soon as its available. In the meantime you can send me any questions as well to the email address mentioned above.

Last but not least: If you wan’t to edit the style of the controls and buttons, you can write some custom CSS. If you don’t know how to do that just let me know in the email and I will give you the code you need. Just be aware that the design has been tested and is intended to be BIG, because it usually works better than smaller call to action buttons and inputs.

Hey Gelu,
this sounds like some specific problem when using it together with the optimize-press theme.

You already switched over the page so I can’t look into it anymore.

I will try to give you further assistance responding to your support email and update this thread with anything relevant for other users.

Thanks and best regards

I am glad that you found what you were looking for and that the custom Code could help you with your individual needs! I am very curious to see the results you got during the next few months.

Thanks a lot for your feedback Wesley, and I am glad that you found value in both the plugin and free email course! Keep up the great work as well, curious to see what you will make out of it

Thank you Bryan! I really appreciate your comments and that you found such great value in both the plugin and free email course. People like you really help me improving upon both the plugin functionality as well the content I publish together with it. So in the end this is not just helpful for me, but for everyone else as well. Thanks again

Thanks for your review and valuable feedback! I am already working on the manual configuration so you can just paste in the form of any email provider. I will let you know once that’s ready!

Hey @perezbox, thanks for chiming in!

I actually checked the log files because of a post I’ve found about them from sucuri.net

So yes this is a VPS.

There weren’t much files in the uploads folder anyway, but I’ve installed the iSecurity Plugin now anyway to block .php files in the upload folders and block access to the xmlrpc.php file.

Do I have to worry that they got access to anything one a higher level like SSH users, the mySQL database, server configuration or something like that? The wordpress install is using it’s own SSH user that only has rights in the install directory and can only connect via SSH keys from localhost.

Thanks Jackie, I got the answer:

The try_files statement is sending all none-existent files to index.php in the web root. I needed to add a second location specifically for the blog to the configuration:

location /blog {
        try_files $uri $uri/ /blog/index.php;
    }

Now it works fine.

(Thanks to Steve E. who pointed this out on StackOverflow)