Scott Bolinger

Executive sounds fancy, thanks Nathan!

Hi, please see the documentation here: https://m1themes.com/m1-setup/

Hi, this is the default webkit behavior. You can override that by adding this to your child theme stylesheet:

.button,
button,
html input[type=”button”],
input[type=”reset”],
input[type=”submit”],
.more-link,
.page-links a {
-webkit-appearance: none;
}

Hey Stephen, this is a weird bug! Not sure why, but try adding this to a child theme style.css file:

#site-navigation {
-webkit-backface-visibility: visible !important;
}

That seemed to fix the issue for me, let me know if that helps.

I think I have a solution for you. Gonna close this thread, email me at https://apppresser.com/contact/

I’m seeing this error now, looking into it…

Congrats!

The splash screen is a native Phonegap feature: https://docs.phonegap.com/en/3.1.0/cordova_splashscreen_splashscreen.md.html#Splashscreen

It shows while the application is loading and then disappears. If there is a blank screen, it sounds like you might not be using it properly.

If you are using Phonegap Build, please see their documentation and make sure everything is configured properly: https://docs.build.phonegap.com/en_US/3.1.0/configuring_icons_and_splash.md.html#Icons%20and%20Splash%20Screens

Hey Martin, this is a known bug in Android 2.3 and below. AppPresser officially only supports Android 4+, but we are going to add support for lower versions as soon as possible.

We have found that adding the iscroll library fixes the scrolling issue for 2.3, but breaks scrolling on iOS. We hope to figure out a fix soon.

Hi, thanks for your feedback. We are planning to add offline functionality in the future, but just because it needs to be online doesn’t mean it’s not a “real app.” There are many apps, including those built by Apple that require an internet connection to work.

This should be fixed now.

Hey Scott, this error should be fixed if you update your theme to the latest version. Please let us know if that solves it, thanks!

Hi, this conflict has been resolved on our end, thanks.

Awesome!

That’s a good idea, it probably won’t happen in version 1, but we’ll definitely put that down as a feature request. Thanks!