Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.
[Brief description ]
- [more description]
- [more description]
- [more description]
===Fixing css issue for trello=== | |
===Ocean-WP=== | |
- button css issues with oceanwp theme - just need to add "button" class on button tag | |
- https://trello-attachments.s3.amazonaws.com/5da59b81e4e03951b237897e/5dbae63402aebe22fc88d05c/50a2f0d2afa0e7c06904c9edb2737208/class_issues.png | |
===Astra Theme=== |
wp_wcfm_daily_analysis | |
wp_wcfm_detailed_analysis | |
wp_wcfm_enquiries | |
wp_wcfm_enquiries_meta | |
wp_wcfm_enquiries_response | |
wp_wcfm_enquiries_response_meta | |
wp_wcfm_following_followers | |
wp_wcfm_marketplace_orders | |
wp_wcfm_marketplace_orders_meta | |
wp_wcfm_marketplace_product_multivendor |
# GET number of orders | |
select count(*)from wp_posts where post_type = 'shop_order'; | |
# DELETE ORDER DATA FROM POSTMETA TABLE | |
delete from wp_postmeta where post_id in (select ID from wp_posts where post_type = 'shop_order'); | |
# DELETE ORDER DATA FROM POSTS TABLE | |
delete from wp_posts where post_type = 'shop_order'; |
Create an unprivileged Linux container (LXC) dedicated to running Wordpress websites.
If you install Wordpress regularly on Linux you can instead simply clone this container.
The Wordpress installation is nothing fancy. It's not multi-site, it's not SSL enabled by default, or anything like that. Just a plain bog-standard Wordpress installation serving a single domain.
<?php | |
/** | |
* WordPress AJAX Frontend Execution. | |
* | |
* Using WP Ajax should not be used from the frontend because response | |
* from `admin-ajax.php` are not cached (including `nocache_headers()`). | |
* Instead, you should add a query var, and then do the `template_include` | |
* routine to select a template that returns JSON. | |
* | |
* A side benefit here is that it makes your site more RESTful. |