classicpress / classic-commerce

A simple but powerful e-commerce platform built for ClassicPress. Forked from WooCommerce and compatible with many Woo extensions.

ClassicPress: The CMS for Creators. Stable. Lightweight. Instantly Familiar.

ClassicPress is a community-led open source content management system for creators. It is a fork of WordPress 6.2 that preserves the TinyMCE classic editor as the default option. It is half the size of WordPress, contains less bloat improving performance, and has no block editor (Gutenberg/Full Site Editing).

For more information, see:

• The official ClassicPress website ›
• The ClassicPress documentation ›
• The ClassicPress governance ›
• Suggest features ›

Contributions

This project exists thanks to all the people who contribute and who have contributed in the past, whether as part of the long history of thousands of contributions to WordPress from many different people, or as contributions to ClassicPress itself.

Would you like to help? Here is how you can start ›

Sponsors

Corporate sponsors that believe in ClassicPress. Become a sponsor › All donations are tax-deductible in the United States.

Financial Contributors

Support the ClassicPress project by making a donation › All donations are tax-deductible in the United States.

Individuals

Organizations

classic-commerce's Issues

Plugin title extends exceeds the borders

Describe the bug
A little bit of eye sore as the plugin name has a visual excess into the border padding.

To Reproduce
Steps to reproduce the behavior:

1. Install the plugin, activate
2. Check the admin menu.

Screenshots

Expected behavior
A clear and concise name needs to be seen as other plugins do.

ClassicPress Version: 0.1.0

New plugin folder name `classic-commerce` breaks functionality for some plugins

Describe the bug
Having to change the folder/plugin folder name to classic-commerce breaks functionality for over 4900+ plugins that use the code below to find out if woocommerce is running active as a plugin.

// it the plugin is active, we're good.
    if (in_array('woocommerce/woocommerce.php', apply_filters( 'active_plugins', get_option('active_plugins')))) {
        return true;
    }

What would be the way forward on this? What's the long term solution for this?

To Reproduce
Steps to reproduce the behavior:

1. Search woocommerce/woocommerce.php via wpdirectory.net

Remove Jetpack + Connected Services by WooCommerce

I am sure Jetpack is going to get a Gutenberg update sometime in the future if it hasn't already. But one of the great features of the Jetpack and WooCommerce combination is the ability to print shipping labels.

Should Jetpack and WooCommerce connection be left for now or replaced? If replaced, what alternatives are there for shipping?

Premium extensions needed

Follow : https://forums.classicpress.net/t/essential-plugins-extensions-for-classic-commerce/1073

• Stripe Payment Gateway (Requires payments to API merchant. Can not be free)
• Reminder system #8 (comment)
• Discount extension
• Mailchimp integration (https://forums.classicpress.net/t/necessary-plugins-extensions-for-classiccommerce/1073/13)

CP & CC specific theme development

I'm about to start on developing CP specific eCommerce theme(s) so I'm kinda digging for reassurances more than seeking support.

At this moment in time my specific concern is on weather all instances of WooCommerce/woocommerce will be changed to reflect ClassicCommerce or will they be maintained for back compat?

Also, is there are project specific roadmap for CC?

Admin notice add user friendly Error message for non Dual CC-Woo Install

I think we need to add an admin notice to make this Error message for meaningful for the ordinary user who might have skipped the documentation and also reduce the support call.

Suggestion:

1. User clicks to install CC.
2. Stop CC install to Detect the WooCommerce ( Need to find a unique function to Woo not in CC ).
3. Throw the notice to deactivate Woo.
4. Notice provides: A link to the plugins deactivation for woo.
5. User can now activate CC.

I know Woocommerce won't be supporting any forks after < WP 5.0. However someone might migrate with an older version of Woo. We have to have this in mind as we move with this ticket.

Originally posted by @bahiirwa in #136 (comment)

Add to FAQ - CC & Woocommerce co-existence

#136 (comment)

Error with unprovided gateways

Describe the bug
A PHP Error is thrown for missing gateway arguments in a loop via the setup wizard on a fresh install. See screenshot attached.

To Reproduce
Steps to reproduce the behavior:

1. Install fresh CP.
2. Turn on define('WP_DEBUG', true);and define('WP_DEBUG_DISPLAY', true);in wp-config.php
3. Install fresh CC plugin from the develop branch
4. Run setup wizard.
5. Error appears on step 2 of the installation.

Isolating the problem (mark completed items with an [x]):

• I have deactivated other plugins and confirmed this bug occurs when only ClassicCommerce plugin is active.
• This bug happens with a default ClassicPress theme active.
• I can reproduce this bug consistently using the steps above.

ClassicPress Environment

``` ` ### CMS Environment ###

Home URL: http://localhost:8888/cc
Site URL: http://localhost:8888/cc
CC Version: 0.1.0
WC Version: 3.5.3
Log Directory Writable: ❌ To allow logging
make /Applications/XAMPP/xamppfiles/htdocs/cc/wp-content/uploads/wc-logs/ writable or define a custom WC_LOG_DIR.

CMS Version: ❌ 1.1.1 - There is a newer version of ClassicPress available (1.1.2)
Multisite: –
Memory Limit: 512 MB
Debug Mode: ✔
Cron: ✔
Language: en_US
External object cache: –

Server Environment

Server Info: Apache/2.4.41 (Unix) OpenSSL/1.1.1d PHP/7.1.32 mod_perl/2.0.8-dev Perl/v5.16.3
PHP Version: 7.1.32 - We recommend using PHP version 7.2 or above for greater performance and security. How to update your PHP version
PHP Post Max Size: 40 MB
PHP Time Limit: 120
PHP Max Input Vars: 1000
cURL Version: 7.53.1
OpenSSL/1.1.1d

SUHOSIN Installed: –
MySQL Version: 5.5.5-10.4.8-MariaDB
Max Upload Size: 40 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔

Database

CC Database Version: 3.5.3
WC Database Prefix: cp_
MaxMind GeoIP Database: ❌ The MaxMind GeoIP Database does not exist - Geolocation will not function. You can download and install it manually from https://dev.maxmind.com/geoip/geoip2/geolite2/ to the path: . Scroll down to "Downloads" and download the "MaxMind DB binary
gzipped" file next to "GeoLite2 Country". Please remember to uncompress GeoLite2-Country_xxxxxxxx.tar.gz and upload the GeoLite2-Country.mmdb file only.

Total Database Size: 1.58MB
Database Data Size: 0.73MB
Database Index Size: 0.85MB
cp_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB
cp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB
cp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB
cp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.05MB
cp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB
cp_woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.03MB
cp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB
cp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB
cp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB
cp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB
cp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB
cp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB
cp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB
cp_woocommerce_log: Data: 0.02MB + Index: 0.02MB
cp_commentmeta: Data: 0.02MB + Index: 0.03MB
cp_comments: Data: 0.02MB + Index: 0.09MB
cp_links: Data: 0.02MB + Index: 0.02MB
cp_options: Data: 0.19MB + Index: 0.02MB
cp_postmeta: Data: 0.02MB + Index: 0.03MB
cp_posts: Data: 0.02MB + Index: 0.06MB
cp_termmeta: Data: 0.02MB + Index: 0.03MB
cp_terms: Data: 0.02MB + Index: 0.03MB
cp_term_relationships: Data: 0.02MB + Index: 0.02MB
cp_term_taxonomy: Data: 0.02MB + Index: 0.03MB
cp_usermeta: Data: 0.02MB + Index: 0.03MB
cp_users: Data: 0.02MB + Index: 0.05MB
cp_wc_download_log: Data: 0.02MB + Index: 0.03MB
cp_wc_webhooks: Data: 0.02MB + Index: 0.02MB

Post Type Counts

page: 6
post: 2
product: 3

Security

Secure connection (HTTPS): ❌
Your store is not using HTTPS. Learn more about HTTPS and SSL Certificates.
Hide errors from visitors: ❌Error messages should not be shown to visitors.

Active Plugins (1)

Classic Commerce: by ClassicPress Research Team – 0.1.0

Settings

API Enabled: –
Force SSL: –
Currency: GBP (£)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

WC Pages

Shop base: #5 - /index.php/shop/
Cart: #6 - /index.php/cart/
Checkout: #7 - /index.php/checkout/
My account: #8 - /index.php/my-account/
Terms and conditions: ❌ Page not set

Theme

Name: ClassicPress TwentySeventeen
Version: 1.0.0
Author URL: https://www.classicpress.net
Child Theme: ✔
Parent Theme Name: Twenty Seventeen
Parent Theme Version: 1.7 – 2.2 is available
Parent Theme Author URL: https://wordpress.org/
Classic Commerce Support: ✔

Templates

Overrides: –
`

</details>

Review functions and classes in edited files

Following #47 and other PRs and issues. This is bound to grow until at least version 1.0.0 release.

There is a need to review how these options, functions, classes and variables affect the other parts of the software besides the files where they are removed.

Classes

• WC_Helper_Updater
• WC_Admin_Addons

Functions

• WC_Helper_Updater::get_updates_count_html()
• WC_Helper_Updater::get_updates_count()
• WC_Admin_Addons::get_featured
• WC_Admin_Addons::output_wcs_banner_block()

Harmonize the color palette

CC uses SCSS and SASS build process for the styling. However, over 90 color variants have been noted in the codebase. In a bid to make a united color palette, we need to harmonize the variants into at least fewer colors with variables as their base to make it easy for changes to be made.

This change is hugely influenced by the color changing from Woo purple to CC green.

Screenshots show the hardcoded color variants in current codebase.

Greys alone have this much

Logo in admin menu size weirdness

Describe the bug
It is happening for me when I am trying to setup Bullet Proof Security. As I visit various screens I get the effect shown below with logo going large.

To Reproduce
Steps to reproduce the behavior:

1. Install BPS pro
2. Click on settings page
3. See error

Screenshots

Expected behavior
Logo should not resize.

Isolating the problem (mark completed items with an [x]):

• I have deactivated other plugins and confirmed this bug occurs when only ClassicCommerce and BPS security plugin is active.
• This bug happens with a default ClassicPress theme active.
• I can reproduce this bug consistently using the steps above.

ClassicPress Environment

alpha.2

Add notice about usage tracking in updater

A 3rd party extension to Codepotent's plugin updater has the facility to track plugin usage as shown in this example:

We need to make sure that users are aware that their usage is being tracked in this way and I would also suggest that we make this an opt-in feature.

We can try to discourage people from opting out by explaining that their data is anonymised and that the data is extremely useful to us during the development and testing stages. But I do think they need to have a choice.

As things stand, this potentially breaches GDPR and possibly other privacy laws too.

IP address on new order is blank

Describe the bug
IP address of new orders not collected.

To Reproduce
Steps to reproduce the behavior:

1. Create a dummy order.
2. Go into admin area and view the new order record
3. Customer IP shows as: "Payment via Direct bank transfer. Customer IP: ::1"

Expected behavior
Should show the customer's IP address, as happens in WooCommerce

Isolating the problem (mark completed items with an [x]):

• I have deactivated other plugins and confirmed this bug occurs when only ClassicCommerce plugin is active.
• This bug happens with a default ClassicPress theme active.
• I can reproduce this bug consistently using the steps above.

ClassicPress Environment
Localhost using XAMPP in Win10 machine
ClassicPress 1.1.0 PHP version: 7.3.5

Copy and paste the system status report from **ClassicCommerce > System Status** in ClassicPress admin.

`
### WordPress Environment ###

Home URL: http://localhost/grantvio
Site URL: http://localhost/grantvio
WC Version: 3.5.3
Log Directory Writable: ✔
WP Version: ❌ 4.9.11 - There is a newer version of WordPress available (5.2.3)
WP Multisite: –
WP Memory Limit: 256 MB
WP Debug Mode: –
WP Cron: ✔
Language: en_US
External object cache: –

### Server Environment ###

Server Info: Apache/2.4.39 (Win64) OpenSSL/1.1.1b PHP/7.3.5
PHP Version: 7.3.5
PHP Post Max Size: 50 MB
PHP Time Limit: 3000
PHP Max Input Vars: 2000
cURL Version: 7.64.0
OpenSSL/1.1.1b

SUHOSIN Installed: –
MySQL Version: 5.5.5-10.1.39-MariaDB
Max Upload Size: 50 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ❌ Your server does not have the SoapClient class enabled - some gateway plugins which use SOAP may not work as expected.
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔

### Database ###

WC Database Version: 3.5.3
WC Database Prefix: wp_
MaxMind GeoIP Database: ✔
Total Database Size: 9.97MB
Database Data Size: 6.76MB
Database Index Size: 3.21MB
wp_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB
wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB
wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB
wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB
wp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB
wp_woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.03MB
wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB
wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB
wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB
wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB
wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB
wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB
wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB
wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB
wp_commentmeta: Data: 0.02MB + Index: 0.03MB
wp_comments: Data: 0.02MB + Index: 0.09MB
wp_links: Data: 0.02MB + Index: 0.02MB
wp_options: Data: 1.05MB + Index: 0.05MB
wp_postmeta: Data: 2.52MB + Index: 1.83MB
wp_posts: Data: 2.52MB + Index: 0.38MB
wp_termmeta: Data: 0.06MB + Index: 0.06MB
wp_terms: Data: 0.02MB + Index: 0.03MB
wp_term_relationships: Data: 0.11MB + Index: 0.08MB
wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB
wp_usermeta: Data: 0.02MB + Index: 0.03MB
wp_users: Data: 0.02MB + Index: 0.05MB
wp_wc_download_log: Data: 0.02MB + Index: 0.03MB
wp_wc_product_meta_lookup: Data: 0.02MB + Index: 0.09MB
wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB
wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB

### Post Type Counts ###

attachment: 1055
nav_menu_item: 98
page: 38
post: 1
product: 520
product_variation: 3
revision: 166
scheduled-action: 3
shop_order: 5
sidebar: 1

### Security ###

Secure connection (HTTPS): ❌
					Your store is not using HTTPS. Learn more about HTTPS and SSL Certificates.
Hide errors from visitors: ✔

### Active Plugins (3) ###

Classic Commerce: by ClassicPress Research Team – 0.1.0
SC Utility: by Alan Coggins – 1.0.10
WooCommerce Mods: by  – 1.0.0 – Not tested with the active version of WooCommerce

### Settings ###

API Enabled: –
Force SSL: –
Currency: AUD ($)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: bundle (bundle)
external (external)
grouped (grouped)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)


### WC Pages ###

Shop base: #1 - /shop/
Cart: #2 - /cart/
Checkout: #3 - /checkout/
My account: #4 - /my-account/
Terms and conditions: ❌ Page not set

### Theme ###

Name: Twenty Seventeen
Version: 2.2
Author URL: https://wordpress.org/
Child Theme: ❌ – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme
WooCommerce Support: ✔

### Templates ###

Overrides: –
`

Update Status report to show both CC and WC version numbers

Is your feature request related to a problem? Please describe.
At present, the status report only shows the WC version and not the CC version. See #143 .

Describe the solution you'd like
Show both versions.

Additional context
Related to issue #143

---

A few minor changes required:

In includes/class-woocommerce.php, below public $version = '3.5.3'; add

public $cc_version = '0.1.0';

In includes/api/v2/class-wc-rest-system-status-v2-controller.php, add

'cc_version' => WC()->cc_version,

in the return array in get_environment_info() (line 614 approx).

In includes/admin/views/html-admin-page-status-report.php (approx line 67), change as follows:

<tr>
  <td data-export-label="CC Version"><?php esc_html_e( 'Classic Commerce version', 'classic-commerce' ); ?>:</td>
  <td class="help"><?php echo wc_help_tip( esc_html__( 'The version of Classic Commerce installed on your site.', 'classic-commerce' ) ); /* phpcs:ignore WordPress.XSS.EscapeOutput.OutputNotEscaped */ ?></td>
  <td><?php echo esc_html( $environment['cc_version'] ); ?></td>
</tr>
<tr>
  <td data-export-label="WC Version"><?php esc_html_e( 'WooCommerce version', 'classic-commerce' ); ?>:</td>
  <td class="help"><?php echo wc_help_tip( esc_html__( 'The version of WooCommerce installed on your site.', 'classic-commerce' ) ); /* phpcs:ignore WordPress.XSS.EscapeOutput.OutputNotEscaped */ ?></td>
  <td><?php echo esc_html( $environment['version'] ); ?></td>
</tr>

Remaining issues with CC + Woo activation logic

After #173 and #175 Classic Commerce should be able to prevent a user from causing fatal errors by trying to activate both CC and Woo at the same time from within the normal UI, on a single-site installation. There are some special cases that are not yet covered:

• If a user is activating and deactivating plugins some other way (e.g. using WP-CLI or a management plugin), they will still be able to cause fatal errors by trying to activate both CC and Woo at the same time.
• I have not tested this activation logic on multisite installations but I suspect users can also cause fatal errors there. Remember that on multisite a plugin can be network activated or only activated for a single site, with different code paths for each case, which means there are more possible cases to test.
• There may still be other ways to break this.

I am not sure if these issues are a high enough priority to fix in the code (I am thinking probably not for version 1 unless we find other things that still don't work correctly). However these caveats do at least need to be documented for users, and this documentation needs to be included in release posts or linked from there so that people who want to try out CC will see it.

Alpha-1 bug with CC Compat plugin

Describe the bug
Testing the Alpha-1 release and encountered the following issue: CC installed and activated with no issue. Notice to download compatibility plugin if installing WooCommerce extensions - downloaded latest version from releases page, installed and activated. Result: CC automatically deactivated with notice "You must deactivate WooCommerce before activating Classic Commerce."

To Reproduce
Steps to reproduce the behavior:

1. Install CC Alpha-1 and activate
2. Download CC Compat, install and activate
3. See error/notice that WooCommerce must be deactivated before activating CC. WooCommerce here refers to the CC Compat plugin and not the original WC version.

Screenshots
If applicable, add screenshots to help explain your problem.

Expected behavior
CC should be able to detect that the active woocommerce/woocommerce.php is the compatibility plugin and not the original WC version.

Fix errors in build process.

Describe the bug
Travis CI fails with bash scripts test in PHP 5.2, 5.3 and 7.2.

• The command "bash tests/bin/phpunit.sh" exited with 1.
• Deprecation warning: Invalid Package Name.

Pinging @nylen

Persistent Notice on installing both plugins.

CC and the compatibility plugin are well installed however, I still get this notice for installing the compatibility plugin. Can it go away on installing both plugins?

Of course closing or dismissing the notice takes it away. It would be better software for being intuitive.

• I have deactivated other plugins and confirmed this bug occurs when only ClassicCommerce plugin is active.
• This bug happens with a default ClassicPress theme active.
• I can reproduce this bug consistently using the steps above.

ClassicPress Environment

``` ` ### CMS Environment ###

Home URL: https://classiccommerce.cc
Site URL: https://classiccommerce.cc
CC Version: 1.0.0
WC Version: 3.5.3
Log Directory Writable: ✔
CMS Version: ✔ You are running ClassicPress Version 1.1.2
Multisite: –
Memory Limit: 256 MB
Debug Mode: –
Cron: ✔
Language: en_US
External object cache: –

Server Environment

Server Info: LiteSpeed
PHP Version: 7.2.26
PHP Post Max Size: 64 MB
PHP Time Limit: 300
PHP Max Input Vars: 3000
cURL Version: 7.62.0
OpenSSL/1.0.2k

SUHOSIN Installed: –
MySQL Version: 10.2.30-MariaDB
Max Upload Size: 64 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔

Database

CC Database Version: 3.5.3
WC Database Prefix: hdwd_
MaxMind GeoIP Database: ✔
Total Database Size: 1.19MB
Database Data Size: 1.09MB
Database Index Size: 0.10MB
hdwd_woocommerce_sessions: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_api_keys: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_attribute_taxonomies: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_downloadable_product_permissions: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_order_items: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_order_itemmeta: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_tax_rates: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_tax_rate_locations: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_shipping_zones: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_shipping_zone_locations: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_shipping_zone_methods: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_payment_tokens: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_payment_tokenmeta: Data: 0.00MB + Index: 0.00MB
hdwd_woocommerce_log: Data: 0.00MB + Index: 0.00MB
hdwd_commentmeta: Data: 0.00MB + Index: 0.01MB
hdwd_comments: Data: 0.00MB + Index: 0.01MB
hdwd_email_log: Data: 0.00MB + Index: 0.00MB
hdwd_icwp_wpsf_audit_trail: Data: 0.02MB + Index: 0.00MB
hdwd_icwp_wpsf_events: Data: 0.01MB + Index: 0.00MB
hdwd_icwp_wpsf_geoip: Data: 0.00MB + Index: 0.00MB
hdwd_icwp_wpsf_ip_lists: Data: 0.00MB + Index: 0.00MB
hdwd_icwp_wpsf_notes: Data: 0.00MB + Index: 0.00MB
hdwd_icwp_wpsf_scanner: Data: 0.00MB + Index: 0.00MB
hdwd_icwp_wpsf_scanq: Data: 0.20MB + Index: 0.00MB
hdwd_icwp_wpsf_sessions: Data: 0.00MB + Index: 0.00MB
hdwd_icwp_wpsf_traffic: Data: 0.00MB + Index: 0.00MB
hdwd_links: Data: 0.00MB + Index: 0.00MB
hdwd_options: Data: 0.81MB + Index: 0.03MB
hdwd_postmeta: Data: 0.02MB + Index: 0.01MB
hdwd_posts: Data: 0.02MB + Index: 0.01MB
hdwd_smush_dir_images: Data: 0.00MB + Index: 0.00MB
hdwd_termmeta: Data: 0.00MB + Index: 0.00MB
hdwd_terms: Data: 0.00MB + Index: 0.01MB
hdwd_term_relationships: Data: 0.00MB + Index: 0.00MB
hdwd_term_taxonomy: Data: 0.00MB + Index: 0.00MB
hdwd_usermeta: Data: 0.01MB + Index: 0.01MB
hdwd_users: Data: 0.00MB + Index: 0.01MB
hdwd_wc_download_log: Data: 0.00MB + Index: 0.00MB
hdwd_wc_webhooks: Data: 0.00MB + Index: 0.00MB

Post Type Counts

attachment: 10
messages: 2
page: 2
plugin_endpoint: 4
post: 2
revision: 6

Security

Secure connection (HTTPS): ✔
Hide errors from visitors: ✔

Active Plugins (7)

Shield Security: by Shield Security – 8.4.4
Classic Commerce: by ClassicPress Research Team – 1.0.0-alpha1
Update Manager: by Code Potent – 1.0.0-rc2
SC Email Log: by Alan Coggins – 1.0.2
SC Utility: by Alan Coggins – 1.1.1
CC Compatibility for Woo Addons: by ZigPress – 9999.0
Smush: by WPMU DEV – 3.3.2

Settings

API Enabled: –
Force SSL: –
Currency: GBP (£)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

WC Pages

Shop base: ❌ Page not set
Cart: ❌ Page not set
Checkout: ❌ Page not set
My account: ❌ Page not set
Terms and conditions: ❌ Page not set

Theme

Name: Simply Light Child
Version: 1.0.0
Author URL: https://simplycomputing.com.au
Child Theme: ✔
Parent Theme Name: Simply Light
Parent Theme Version: 1.0.6
Parent Theme Author URL: https://simplycomputing.com.au
Classic Commerce Support: ✔

Templates

Overrides: –
`

</details>

Add ClassicPress starter themes into CC

WooCommerce already supports theme versions from twentyten all the way to twentyseventeen. We should add this for ClassicPress themes too.

Question is whether we should leave all the versions or just have from twentyfifteen to twentyseventeen which come with ClassicPress on install.

Remove Setup Wizard

I have never found the Setup Wizard to be useful. I prefer to go into settings and do it manually, and I would rather consider extensions carefully as I build the shop, not be choosing them first thing, up front. In fact, the Setup Wizard has always seemed to me as a process primarily designed to push certain products, which then require you to install JetPack to support them.

I am suggesting we drop the Setup Wizard completely from Classic Commerce.

Delete the readme.txt?

This is pending what ClassicPress plugin directory will require. This has lots of WP-WooCommerce content.

Simplify the "Extensions" area

The extensions area currently provides a place to find and download extensions, both free and paid. It also has a tab to manage WooCommerce Subscriptions.

Classic Commerce has no way of knowing which extensions will work, so we shouldn't be seen to be presenting or recommending anything at this stage.

I am suggesting we replace this page with a simple text page with some basic information and maybe a disclaimer. It can have a link to WooCommerce extensions, but we should make it clear that finding, researching and testing suitable extensions is up to the individual user.

At a later stage we might want to add a list of extensions that are built for CC, or have declared support for CC.

This is an example:

Remove Wootenberg/Gutenberg

Remove scripts and styles that support Gutenberg/Block Editor since ClassicPress does not support these.

Don't hide options so they only show on hover.

Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to hover over some blank area of the screen to make a menu appear. This is a trendy Gutenberg-style idea that is completely pointless and bad UX.

Describe the solution you'd like
When looking at the product variations, the available options (move, open and remove) should be visible right there on the screen. Also the open button is tiny and could be a better size to make it easier to hit.

Describe alternatives you've considered
No alternatives

Additional context
This is how it looks now.

In order to see the options you have to hover over the end of the line... which is useful if you know about it.

There is nothing wrong with having these available and in view all the time.

To achieve this I have added a function to my functions.php file:

 add_action('admin_head', 'sc_custom_css');

		function sc_custom_css() {
			echo '<style>
				.wc-metaboxes-wrapper .wc-metabox h3 a.delete {
				    visibility: visible;
				}

				.wc-metaboxes-wrapper .wc-metabox h3 .handlediv {
				    visibility: visible;

				}

				.wc-metaboxes-wrapper .wc-metabox .handlediv::before {
				    font: 400 30px/1 Dashicons;
				    padding: 6px 6px;
				}

				.woocommerce_attribute h3 .sort, .woocommerce_variation h3 .sort {
				    visibility: visible;
				}
			}
			</style>';
		}

When activating Classic Commerce, deactivate WooCommerce

As described in the title: When CC is activated, WooCommerce should be deactivated automatically.

This should only be done if the woocommerce folder actually contains WooCommerce, not the compatibility plugin described in #131 (comment).

Display dismissible admin notice if CC detects that WC compat not installed

Is your feature request related to a problem? Please describe.
The CC compat plugin will need to be installed and active to ensure compatibility with many plugins. The plugin will be a separate install to CC, the intention being that the user only installs it if plugins need it. This will need to be made clear to the user.

Describe the solution you'd like
If any of the methods show below return false, display a dismissible admin notice to inform the user that the compat plugin may be required, along with a link to the download location.

Describe alternatives you've considered
Possibly also worth considering a link to an internal and/or external help page.

Additional context
Only those plugins using any of the following detection methods will need the compat plugin:

	Method
1	in_array( 'woocommerce/woocommerce.php', self::$active_plugins ) || array_key_exists( 'woocommerce/woocommerce.php', self::$active_plugins );
2	in_array( 'woocommerce/woocommerce.php', apply_filters( 'active_plugins', get_option( 'active_plugins' ) ) )
3	is_plugin_active( 'woocommerce/woocommerce.php' )

What is ClassicCommerce’s roadmap?

What direction is ClassicCommerce taking in terms of development and customer satisfaction?

Add FAQ explaining how to uninstall Woocommerce

Should there be an additional note in the FAQ explaining this and how to "uninstall" WooCommerce? - some users may not know what uninstall means let alone how to do it.

Originally posted by @zulfgani in #150 (comment)

Simple "To Do" list for alpha release

To Do List for Alpha Release

• Change color coding to match logo
• Add the CC dashicon for main admin menu
• Change title in main admin menu from WC to CC (without breaking the styling)
• Change version of CC - currently shows 3.5.3 on the status report
• Remove includes>admin>helper files because they are part of Woocommerce subscriptions and are no longer needed? https://docs.woocommerce.com/document/woocommerce-helper/
• Harmonize the color palette(#178).
• Remove all css related to removed items from install wizard (#179)
• Remove all tests for woo services and jetpack server calls. (#179)
• Remove all "wootenberg" promotions eg admin\views\html-notice-wootenberg.php
• Remove wp.org needed files

Necessary Plugins/Extensions

It just occurred to me that there are other needed plugins and extensions that may need to be considered before version 1.0.0 is released. Let's make a running list of necessary plugins/extensions needed for version 1.0.0.

• Stripe
• Paypal
• Paypal Pro
• Invoicing
• vat ID
• Mailchimp
• Shipping Labels

Moved to premium plugins needed
- [ ] reminder system Ref #19
- [ ] Stripe Ref #19

Follow: https://forums.classicpress.net/t/essential-plugins-extensions-for-classic-commerce/1073

Remove redundant update code

Regarding includes/wc-update-functions.php and includes/class-wc-install.php, is there a lot of redundant code we can get rid of?

Could everything except the code added above (i.e. everything not related to WC 3.5.3) be removed from both of these files?

Can anyone see any adverse implications of doing this?

This in itself brings a new issue. There is code for WC < 3.0. Do we want to maintain this? If we have an answer for this we can then sort out that issue of redundant code too.

Originally posted by @bahiirwa in #143 (comment)

Link to CC forums is wrong in README.md

The link in

You can also use the dedicated support area on the ClassicPress community forum.

points to

https://forums.classicpress.net/c/support/classic-commerce/

instead of

https://forums.classicpress.net/tags/classic-commerce

Need for new classic-commerce.pot?

Prerequisites

• I have searched for similar issues in both open and closed tickets and cannot find a duplicate
• The issue still exists against the latest master branch of ClassicCommerce on Github
• I have attempted to find the simplest possible steps to reproduce the issue
• I have included a failing test as a pull request (Optional)

Steps to reproduce the issue

PR #52 is aimed at making new text-domain for Classic Commerce, However this raises a new issue of whether we need a new classic-commerce.pot file since the strings for translation are changing too.

Pre Version 1.0.0 Release

At the moment #2, #3, #5 and #7 are currently on the docs for version 1.0.0 release. Are there any other features or known bugs that should be added to version 1.0.0?

Update README

Change branding & new Logo

• Change WooCommerce logos in installation wizard
• Change color branding.
• Add new logo/svg for plugin admin menu.

Remove data tracking

WooCommerce does data tracking and requests for it on installation of the plugin. This information is routed to their servers. Does CC need this? I am of the view we should eliminate this request and option from all versions of the plugin.

• The issue still exists against the latest master branch of ClassicCommerce on Github

Steps to reproduce the issue

1. Install plugin and activate.
2. A request in available to track information on first options.

Expected/actual behavior

We do not need to track sensitive shop data.

Custom folder in child theme should be recognised whether named WC or CC

Describe the current situation
An existing site may have a woocommerce folder set up in a child theme for custom versions of some of the files. If this is changed to be named classic-commerce it is not recognised. So this folder currently still needs to be called woocommerce, even when using CC.

Additional context
It's a good idea that the woocommerce folder is recognised so as not to break existing sites that already have this folder in place. But anyone setting it up from scratch would probably call it classic-commerce. Can it be set up to to recognise either of them?

Edit Doc Blocks

Remove ajax 'woocommerce_rated'

This is not bug. Following #35 There needs to be a follow up on the Ajax call for woocommerce_rated

Action point: Check if this is used in any other files or remove from the JavaScript.

Current status!

@parkerj Thank you for taking on this mammoth task.

Are there minor things that we can help with so that we can progress along and get some traction on the project?

Would love to see this one come to fruition as I would not want to start developing with WooCommerce then have to switch over later.

Add a media uploader for Placeholder image

For better user experience, I thought it would be helpful to have an ordinary media uploader instead of a text/url field. This will make it "Fool proof" and create consistency in the use of ClassicPress in-built components.

Plugin Archiving

Need to properly document the different files and functions as we move to version 1.0.0
This issue tracks the archiving process since it has many hands on deck.

Change @since int to @since WC-int
Change @package Woocommerce to @package ClassicCommerce

Folders

• i18n
• includes
• templates
• tests

New tagline

Since we are re-branding with logos and colors, We surely need a new tagline.

"An eCommerce toolkit that helps you sell anything. Beautifully." is by Woocommerce. What would you say is our new sales line?

Ability to have auto generated Zip Codes

Having auto complete options for state are well done but issue is that there are no auto generated zip codes to match the state on signing up the shop. See image below

It would be very nice to have zip codes generated on input of states just like country currencies codes are input on adding the country.

Add "delete all data" option when removing CC

Is your feature request related to a problem? Please describe.
Currently WC and CC do not delete data / database tables when they are uninstalled. This can leave a lot of useless data clogging up the database.

Describe the solution you'd like
An option button that gives the user the choice of whether or not they want the data to be removed, set to "no" by default. An option to export the data (in a format that can be reimported) before removing it would also be useful.

Describe alternatives you've considered
It's possible to remove the data manually from the database but this should not be necessary and would be beyond the means of most end users.

Additional context
WC and CC both give a scary warning that data will be deleted but this doesn't happen. This warning is misleading.

See also #136 (comment)

Change version of WooCommerce reported by CC to 3.5.3

Describe the bug
See #131.

Plugins use a number of different methods to determine the version of WC that is active. Such plugins often require a minimum version of WC in order to a) activate and/or b) function correctly. At present, Classic Commerce reports version 1.0.0, the version of CC, rather than the version of WC it was forked from. Consequently, many plugins fail to activate.

This requires changes to the following as a minimum:

• $woocommerce->version
• WC_VERSION
• WOOCOMMERCE_VERSION
• woocommerce_db_version (options table)

To Reproduce
Try to activate a plugin the requires WC >= 3.0 (for example).

Screenshots
Example:

Expected behavior
Plugins checking for WC <= 3.5.3 should activate without error.

Remove .wordpress.org folder

As mentioned in #135

Can't activate CC after deactivating WC

Describe the bug
Can't activate CC after deactivating WC (version 3.7.1)

To Reproduce
Steps to reproduce the behavior:

1. Install CC on a site with WC activated
2. Deactivate WC
3. Try and activate CC
4. See error message "You must deactivate WooCommerce before activating Classic Commerce." It also shows a message saying "Plugin activated."
5. CC is not activated.

Screenshots

Expected behavior
CC should be able to be activated after WC deactivated.

Isolating the problem (mark completed items with an [x]):

• I have deactivated other plugins and confirmed this bug occurs when only ClassicCommerce plugin is active.
• This bug happens with a default [ClassicPress[ WP theme active - 2017.
• I can reproduce this bug consistently using the steps above.

ClassicPress Environment

Unable to access

Notice: Undefined variable: count_html

Describe the bug
The removal of $count_html = WC_Helper_Updater::get_updates_count_html(); from includes/admin/class-wc-admin-menus.php is now throwing a PHP Notice on the dashboard as follow
Notice: Undefined variable: count_html in C:\Users\zulfn\Desktop\UniServerZ\www\featherlite\wp-content\plugins\classic-commerce\includes\admin\class-wc-admin-menus.php on line 131

To Reproduce
Developing locally with WP_DEBUG set to true
To continue developing with the latest version I've commented out line 31 of the same file for now.

Expected behavior
No PHP Errors, Notices or Warnings should be generated upon plugin activation.

Isolating the problem (mark completed items with an [x]):

• [x ] I have deactivated other plugins and confirmed this bug occurs when only ClassicCommerce plugin is active.
• [x ] This bug happens with a default ClassicPress theme active.
• [x ] I can reproduce this bug consistently using the steps above.

ClassicPress Environment

``` ` ### CMS Environment ###

Home URL: http://localhost/featherlite
Site URL: http://localhost/featherlite
CC Version: 3.5.3
Log Directory Writable: ✔
CMS Version: ✔ You are running ClassicPress Version 1.1.1
Multisite: –
Memory Limit: 256 MB
Debug Mode: ✔
Cron: ✔
Language: en_US
External object cache: –

Server Environment

Server Info: Apache
PHP Version: 7.1.1 - We recommend using PHP version 7.2 or above for greater performance and security. How to update your PHP version
PHP Post Max Size: 12 MB
PHP Time Limit: 600
PHP Max Input Vars: 1000
cURL Version: 7.51.0
OpenSSL/1.0.2j

SUHOSIN Installed: –
MySQL Version: 5.6.35
Max Upload Size: 12 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ❌ Your server does not have the SoapClient class enabled - some gateway plugins which use SOAP may not work as expected.
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔

Database

CC Database Version: 3.5.3
WC Database Prefix: td_
MaxMind GeoIP Database: ✔
Total Database Size: 5.54MB
Database Data Size: 4.26MB
Database Index Size: 1.28MB
td_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB
td_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB
td_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB
td_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.05MB
td_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB
td_woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.03MB
td_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB
td_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB
td_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB
td_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB
td_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB
td_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB
td_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB
td_woocommerce_log: Data: 0.02MB + Index: 0.02MB
td_commentmeta: Data: 0.02MB + Index: 0.03MB
td_comments: Data: 0.02MB + Index: 0.08MB
td_cpseo_404_logs: Data: 0.02MB + Index: 0.02MB
td_cpseo_internal_links: Data: 0.02MB + Index: 0.02MB
td_cpseo_internal_meta: Data: 0.02MB + Index: 0.00MB
td_cpseo_redirections: Data: 0.02MB + Index: 0.02MB
td_cpseo_redirections_cache: Data: 0.02MB + Index: 0.02MB
td_links: Data: 0.02MB + Index: 0.02MB
td_options: Data: 2.02MB + Index: 0.05MB
td_postmeta: Data: 1.52MB + Index: 0.17MB
td_posts: Data: 0.06MB + Index: 0.06MB
td_termmeta: Data: 0.02MB + Index: 0.03MB
td_terms: Data: 0.02MB + Index: 0.03MB
td_term_relationships: Data: 0.02MB + Index: 0.02MB
td_term_taxonomy: Data: 0.02MB + Index: 0.03MB
td_udmanager_download_history: Data: 0.02MB + Index: 0.05MB
td_udmanager_plugins: Data: 0.02MB + Index: 0.03MB
td_udmanager_user_entitlements: Data: 0.02MB + Index: 0.11MB
td_usermeta: Data: 0.02MB + Index: 0.03MB
td_users: Data: 0.02MB + Index: 0.05MB
td_wc_download_log: Data: 0.02MB + Index: 0.03MB
td_wc_webhooks: Data: 0.02MB + Index: 0.02MB

Post Type Counts

attachment: 49
cmm4e_menu: 1
cmm4e_menu_theme: 1
cp_theme_repo: 1
custom_css: 2
customize_changeset: 55
elementor_library: 2
elementskit_template: 1
gp_elements: 3
happyform: 1
hf_composer: 1
insertpostads: 2
nav_menu_item: 23
next-megamenu: 1
opal_menu_item: 1
page: 17
post: 5
product: 18
product_variation: 7
revision: 45
tailor_templates: 1

Security

Secure connection (HTTPS): ❌
Your store is not using HTTPS. Learn more about HTTPS and SSL Certificates.
Hide errors from visitors: ❌Error messages should not be shown to visitors.

Active Plugins (9)

Secure WP Admin: by wpexpertsio – 1.3
Browser Shots: by Ben Gillbanks – 1.7.4
Classic Commerce: by ClassicPress Research Team – 0.1.0
Customize Object Selector: by XWP – 0.4.2
FeatherLite Controls: by GetFeatherLite – 1.0.0
Featherlite Parallax Hero: by ClassicDesigner – 1.0.0
Show Current Template: by JOTAKI Taisuke – 0.3.0
StorePage: ClassicCommerce Store Page: by CPEngineered – 1.0.0
Customize Widget Sidebar Meta: by Weston Ruter
XWP – 0.1.0

Settings

API Enabled: –
Force SSL: –
Currency: GBP (£)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

WC Pages

Shop base: #246 - /shop/
Cart: #247 - /cart/
Checkout: #248 - /checkout/
My account: #249 - /my-account/
Terms and conditions: ❌ Page visibility should be public

Theme

Name: FeatherLite
Version: 1.0.0
Author URL: https://getfeatherlite.com
Child Theme: ❌ – If you are modifying Classic Commerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme
Classic Commerce Support: ✔

Templates

Overrides: –
`

</details>