开发者 | Marcelismus |
---|---|
更新时间 | 2024年3月8日 22:31 |
捐献地址: | 去捐款 |
PHP版本: | 4.7 及以上 |
WordPress版本: | 6.3 |
版权: | GPLv3 |
版权网址: | 版权信息 |
The server must run at least PHP 5.3 and support cURL and mb_eregi.
Yes, all elements of the WP-Appbox can be customized via CSS. It is also possible to deactivate the CSS stylesheet of the plugin in the settings. In addition, you can create your own templates for the output (see below).
You can simply copy the existing standard templates (folder "tpl") into your theme folder. The files can be given the following names:
Basically, yes. However, the CSS of the WP-Appbox has to be implemented manually into your AMP page. How this works depends on your plugin.
The QR code generator from Google has the peculiarity that the QR codes are created only throughout the fixed size. The shorter the URL, the smaller the code becomes and the higher the value "margin". This cannot be corrected with a "margin=0" value. Whether it is a feature or a bug is discussed in the Google Groups.
Unfortunately Google only loads the first screenshot into the HTML output of the Chrome Web Store, all other screenshots are dynamically reloaded. Therefore the output of several screenshots via WP-Appbox is not possible at the moment.
Basically: yes. But it depends on the settings. The plugin itself does not store any user data. However, external images from Apple, Google, Amazon and Co. are integrated. Depending on the interpretation of the DSGVO, this is problematic. If you don't want to supplement your data protection information, you can use two possible options:
A first implementation is available. However, this is experimental in nature and is not officially supported. With WordPress 6.2 there are problems with the block, but so far I have not found a solution. Classic Editor is therefore recommended ;)
The PA-API 5.0 has a request limit, which is currently still very buggy. Also, unlike version 4.0, no images (icons and screenshots) are returned for Android Apps and Alexa Skills. Therefore I have currently decided to remove the PA-API. Should Amazon extend version 5.0, it will of course be implemented again.
Amazon has a very strong and "good working" bot detection. Therefore I had to resort to this workaround. It is not perfect, but the only alternative would be to remove Amazon from the WP appbox completely... :-/