WebSuite PWA
| 开发者 |
publisherstoolbox
johan101 drmzindec |
|---|---|
| 更新时间 | 2021年9月9日 14:57 |
| PHP版本: | 7.1 及以上 |
| WordPress版本: | 5.4.2 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
安装:
- Go to the Plugins, Add new.
- Search WordPress for WebSuite PWA then press Install now.
- Activate plugin.
- Enable PWA and Set plugin settings.
- Enjoy.
- Locate your WordPress install on the file system
- Extract the contents of
publishers-toolbox-pwa.zipintowp-content/plugins - In
wp-content/pluginsyou should now see a directory namedpublishers-toolbox-pwa - Login to the WordPress admin panel at
http://yoursite.com/wp-admin - Go to the Plugins menu.
- Click Activate for the plugin.
- Go to the PWA settings page.
- You are all done!
常见问题:
I have enabled WebSuite PWA, but I still see the desktop theme on my smartphone
If you are using a caching plugin, please ensure that it is disabled or configured correctly. Some additional settings on the cache plugin might be required to correctly enable the mobile detection from WebSuite PWA. = What devices and operating systems are supported by my mobile web application? WebSuite PWA is supported on iOS and Android smart phones and tablets. Compatible browsers: Safari, Google Chrome, Android - Native Browser.
How can my readers switch back to the desktop theme from my mobile web application?
The side menu of the mobile web application contains a Switch to website button that will take readers back to the desktop theme. Their option will be remembered the next time they visit your blog.
How can my readers switch back to the mobile web application from the desktop theme?
A link called Switch to mobile, will be displayed in the footer of your desktop theme, only for readers that are viewing the site from a supported device and browser. Their option will be remembered the next time they visit your blog.
I want to temporarily deactivate my PWA application. What steps must I follow?
The PWA application can be deactivated from the Settings page on the admin panel. This option will not delete any settings that you have done so far, like customizing the look & feel of your application, but mobile readers will no longer be able to see it on their devices.
What is the difference between my PWA application and a responsive theme?
A responsive theme is all about screen-size: it loads the same styling as the desktop view, adjusting it to fit a smaller screen. On the other hand a PWA application combines the versatility of the web with the functionality of touch-enabled devices and can support native app-like features such as:
- Apps load nearly instantly and is reliable, no matter what kind of network connection your user is on.
- PWA install banners and gives users the ability to quickly and seamlessly add your mobile app to their home screen, making it easy to launch and return to your app.
- Web push notifications makes it easy to re-engage with users by showing relevant, timely, and contextual notifications, even when the browser is closed.
- Smooth animations, scrolling, and navigation keeps the experience silky Smooth.
- Secured via HTTPS.
更新日志:
- Performance upgrades.
- Homepage loading upgrades.
- Readme updates.
- Removed all legacy code.
- Update amp html link.
- Remove amp home html link.
- Remove amp category html link.
- Fixed AMPHTML tag link on archive pages.
- Added rest API link for PWA configs.
- Updated tags redirection.
- Updated response code detection.
- Updated banner asset.
- Fixed homepage amphtml tag.
- Tested with latest WordPress version.
- Fixed Push notification messages.
- Added search fields customisation to plugin admin.
- General code cleanup and bug fixes.
- Added homepage check for ?noapp.
- Added interim ?noapp to custom post types.
- Made fields more descriptive.
- Added additional descriptions to fields.
- Cleaned up legacy fields.
- Minor code improvements and checks.
- Improved verification checks for multi sites.
- Improved error handling.
- Improved multi site options handling.
- General code improvements.
- Fixed script conflict.
- Improved Pages selection and ordering.
- Improved Category selection and ordering.
- Added GDPR fields for EU users.
- General code improvements.
- Tested WordPress version 5.4
- Upgrade version to 2.2.8
- Added post ad list option.
- Added post author display.
- Fixed Theme swap.
- Fixed version.
- Added host CDN overwrite field for caching plugins images.
- Fixed OG Meta tag script inclusion in Facebook share.
- Added host CDN overwrite for caching plugins.
- Fixed OG Meta tag issue.
- Fixed AMP trailing slash.
- Fixed Ad slots.
- Fixed multisite header origin.
- Added AMP support.
- Fixed legacy issues.
- Minor bug fixes on info messages.
- CloudFront mobile detect update.
- Fixed html characters in menu.
- Fixed fallback script.
- Fixed push notifications excerpt escape characters.
- Updated fallback script.
- Updated App routes.
- Fixed legacy manifest generator.
- Implemented better version checking.
- Fixed plugin update file reset.
- Fixed minor display bugs.
- Removed debug log in live mode.
- Minor bug fixes and improvements.
- Fixed push notifications.
- Switched preview to live mode.
- Added instant preview for display settings.
- Added premium licence detection.
- Added push notification sending for premium plugin owners.
- Simplified display settings for light and dark themed apps.
- Bug fixes for sortable fields.
- Bug fixes for input fields.
- Performance updates.
- Fixed URL issue on ajax calls.
- Assets update.
- Wordpress version update.
- Update CDN endpoint field.
- Load fallback script in header.
- Bug fixes.
- Fix admin link.
- Add jquery fallback script for mobile detection and bypass weird caching issues on some servers.
- Updated Application Endpoint overwrite to use CDN if needed.
- Bug fixes.
- Rewrite router for better loading on legacy and standardization.
- Rewrite router for better loading on legacy and standardization.
- Legacy loader routing fix.
- Legacy CDN loader added for old options.
- Legacy check updated.
- Minor bug fixes.
- Bug fixes.
- Upgraded UI/UX.
- Upgraded codebase to PHP 7.1 compatibility.
- Upgraded multisite loading.
- Improved memory handling.
- Security patches for libraries.
- Updated documentation.
- Fixed general bugs and layout issues on admin area.
- Added ajax loading and fallback options.