Originally Posted by
lankeeyankee
The status updating is there in the config and it is being updated in the db. Perhaps the init file didn't get updated in 1.1? Because it's also showing a config version number of 1.0 on line 100.
Correct, it is still missing in the init_ra_config.php -
I still run my SQL patches, this will add that opti
PHP Code:
INSERT INTO configuration (configuration_id, configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added, use_function, set_function) VALUES
(NULL, '<strong>Admin</strong> Update Order Comments option', 'ORDER_COMMENTS_RMA_OPTION', 'true', 'Update <strong>Admin</strong> Order Comments upon RMA Success',@configuration_group_id, 30, now(), NULL, 'zen_cfg_select_option(array(''true'', ''false''), ');
Originally Posted by
lankeeyankee
The one bug that comes to mind, and it's just a small point, is the use of html break tags in the text section of the admin email in the header file. That breaks the layout of the text email and needs to be changed to a newline instead. We only use text admin emails so that came to light right away in testing.
We did not update the email portions of this plugin, that code was from the original plugin. I do have cleaner email code I had planned to put in the next version.
Originally Posted by
lankeeyankee
The other couple are small, too, mostly format/layout issues, but I am not at my computer that has my notes on it right now.
Please do share - also remember that I tested this on a clean install of Zen Cart, so anyone with a custom template may have to make minor layout, css changes.
Originally Posted by
lankeeyankee
I remember that I was thinking of changing to a config option to add a phone number so the language file doesn't need to be edited to help avoid confusion for newer users who will be wondering where 1.111.111.1111 can be changed and haven't yet discovered the joys of the developers toolkit.
So many plugins with define files. includes/languages/english/YOUR_TEMPLATE_NAME/returns.php
I agree this can simply be changed to pull the Telephone - Customer Service from within admin > My Store
Originally Posted by
lankeeyankee
Or at least put something in the readme about where to change it as well as the body of the customer email. I always err towards making things as well-explained as possible with new users in mind to keep their frustration levels down and minimize the amount of time spent getting the module up and running on a live site.
Time is something we all wish we had more of.
Originally Posted by
lankeeyankee
I will report back the other little things I found to help tighten it up once I get back to my other laptop. It's nothing major, overall this works really well and is a vast improvement over the original version and has already come in pretty handy in the couple days it's been running live. Much more professional customer-facing-wise and more streamlined admin-wise.
I would of liked your initial post to have said that!
Originally Posted by
lankeeyankee
Once I get the db table set up to store the RMA details it will allow tracking of the RMA process and the ability to set an RMA as closed once the process is complete with an admin page to see all RMAs and their progress/status to help admins keep track of what's going on, post comments and details, and enter refund/exchange transaction records, which I think will be a very useful feature. This is the table the daily cron will pull from to check the expiration date of an RMA and take action if needed.
The plugin already updates ORDER_STATUS to say something like "RMA Request Received" if that's what you add to ADMIN > Localization > Order Status
I think it is feasible to add more order status's as a shop owner "RMA Request Received", "RMA Received at Warehouse", "RMA Processed", "RMA Complete - Refund Issued", "RMA Complete - Replacement Shipped"
I think simply using that date added from the order_status_history table against date_purchased from the orders table might be a easier way to reject or deny form submission.
Originally Posted by
lankeeyankee
I will need help testing that part out on 1.5.x since there will be an admin interface.
Send away - I will test.
Originally Posted by
lankeeyankee
I will also want some feedback about features that should be included, like whether to have the ability to set comments/entries as public so the customer can track the RMA from the store side. I think this would be a good idea but would like input from other users.
No way - maybe you should have reporterd all this during the WHOLE MONTH we discussed the development of Flexible Return Authorization
Bookmarks