dingo-d / woo-solo-api Goto Github PK

Currently, the offers are stored in the uploads folder. This should be made such that they are maybe just temporarily saved and then sent, after sending they should be deleted.

Could be a gdpr issue, although I need to add the notice that gdpr is not something I need to look after.

@dingo-d Add an issue template with the Release checklist.
See https://make.wordpress.org/cli/handbook/contributions/release-checklist/
(note query parameters)

From #107

To do:

• Explore the implementation of interfaces in the plugin (with the autoloader).
• Add wp-browser test suite
• Modify the expiry date of the offers/invoices (rok_placanja)
• Pull the translation of customer note based on the language selected
• Issue: if 2 transactions are marked as complete, only one will send the call to solo API for completion.
• Issue: When changing the order from on hold to completed in the order screen the API call is made again (support link)
• Link the invoice from the Solo service with the WooCommerce invoice (support link)
• Make company field mandatory if R1 type of invoice is selected (support link)
• Check if the offer/bill is created twice (support link)
• Check the possible rounding errors (support link)
• API call made twice (using Corvuspay integration) (support link)
• Check the Braintree integration
• Add acceptance criteria

Opened PR: #19

For some reason, the language that is set during sending of the json to SOLO API is affecting the whole site, so once that's done the language should be reverted

Currently one can select a payment option (Cash, Card, Check...) and this is applied globally. So, if someone has different payment gateways in woocommerce, they all need to be the same.

A use case would be a web page that allows payment via Credit card, but also via bank transaction. Now, even a bank transaction option results in an invoice that is marked as credit card payment.

IMHO, one should be able to select 'fiscal option', 'type of the document' and 'payment option' for every gateway. As an example:

• PayPal - fiscalized, invoice, credit card
• WSpay - fiscalized, invoice, credit card
• bank transfer - not fiscalized, offer, bank transaction

This should be

if ($status < 200 && $status >= '400') {

• Update CHANGELOG.md with relevant changes
• Update Readme.txt and Readme.md files
  • Update all the tags, especially Stable tag
  • Update hooks if added
  • Update FAQ if needed
• Update main plugin file - all the tags
• Make sure everything works in the production environment and development environment
• Make sure plugin translation is working
  • Make sure all strings are translatable, and properly translated
• Fix all lint issues
• After all of the above has been fixed tag the new version in the GH
• Commit the new version to the wordpress.org SVN repo

The following are features to be added in the update

To do:

• Add scroll to the Solo API order details table in the admin
• Add better error handling in case a database operation fails
• Add a measure field to every item and read that value from there, fallback to options if none is set (support link)
• Add the option to execute the call on checkout or manually for every payment gateway (support link)
• Fix the trigger on GH actions
• Add qr code generation in the notice (support link)
• Add a filter to the tax calculation so that third-party plugins can hook into it if they need to modify it based on a certain criterion like country based price calculation (support link)
• Update fiters so that they include woocommerce order in it (for manipulation) (support link)
• Add a way to detect if WooCommerce is active and disable the plugin gracefully if it's not active (support link)
• If an invoice name contains slashes in the name, the PDF doesn't get generated and attached to the email
• Add a filter for the request data so that it can be modified before sending to API #76
• Add 10up GH action for code deploy to wp.org (https://github.com/10up/action-wordpress-plugin-deploy)
• Add new status change check when the request will be made to the API (support link)

Add travis integration for php checks.

[26-Nov-2021 11:33:37 UTC] PHP Warning: Undefined array key 0 in /home/dudicacom/stage1.dudica.com/wp-content/plugins/woo-solo-api/src/BackgroundJobs/SendCustomerEmail.php on line 50
[26-Nov-2021 11:33:37 UTC] PHP Warning: Undefined array key 1 in /home/dudicacom/stage1.dudica.com/wp-content/plugins/woo-solo-api/src/BackgroundJobs/SendCustomerEmail.php on line 51
[26-Nov-2021 11:33:37 UTC] PHP Warning: Undefined array key 2 in /home/dudicacom/stage1.dudica.com/wp-content/plugins/woo-solo-api/src/BackgroundJobs/SendCustomerEmail.php on line 52
[26-Nov-2021 11:33:37 UTC] PHP Warning: Undefined array key 3 in /home/dudicacom/stage1.dudica.com/wp-content/plugins/woo-solo-api/src/BackgroundJobs/SendCustomerEmail.php on line 53
[26-Nov-2021 11:33:37 UTC] PHP Warning: Undefined array key 4 in /home/dudicacom/stage1.dudica.com/wp-content/plugins/woo-solo-api/src/BackgroundJobs/SendCustomerEmail.php on line 54

Issue: https://wordpress.org/support/topic/check-if-you-want-the-invoice-to-be-fiscalized-not-saving

For some reason, the toggled option isn't being passed as a boolean when saved but is stored as null, which won't pass the validation.

Pozdrav,

koristim Vas plugin na jednoj instalaciji pa me zanima postoji li neki filter/nacin da dinamicki posaljem tip racuna.

Naime na checkout stranici imam custom dropdown za odabir tipa subjekta (privatna osoba | tvrtka | javna ustanova) i ovisno o tome se prikazuju input fieldovi za OIB/naziv/ime/prezime itd. Ovisno o tom odabiru ja bi volio imati mogucnost poslati tip R racuna za privatnu i R1 za ostale tipove.

Koliko sam ja ovako uspio vidjeti trenutno se gleda iskljucivo option u postavkama SOLO plugina, ali mozda sam nesto previdio.

Hvala unaprijed!