long working on perfect SuiteCRM installation. Now i want to Open up another thing - automatic Invoice Creation, based on an api call, as i actually are not very into api programming (but i am experienced in php some years ago) so i am running through dark forrest at the moment and propably I need your start-push.
how can i call the api properly for getting done first steps?
how can i start creation of a new invoice by it?
can i also find some services/products in suitecrm database for sum it up with the given numbers of the api call or do i need other ways for this and is it possible to filter these feedback-values?
(e.g i have a product 2018-05-name, 2019-02-name, 2019-08-name, and 2020-04-name it should use 2020-04-name as it is the last?
non dev question: how can i set up a standard due date in suitecrm?
how can i automatically send emails with these invoices? Or can i show all “created but not send invoices” somehow? (i actually just saw paid and non paid in reports yet)
There are a number of ‘gotchas’ with this that I’ve highlighted over the past few weeks. Once you have the API working, then you can move forward to the next bit (the invoicing) which will depend on your specific setup.
Did you manually copy over your .htaccess?
Have you got mod_rewrite enabled?
Have you configured it correctly - you need to have created the keys, and have an https connection for the OAuth to work:
How to use with Postman
Once you have done this, you may hit another issue in that if you copied the .htaccess over, then it won’t work correctly, as the config in the web installer is not correct. See:
As a result, I’ve detailed the alternative URLS at the end of:
I guess that I ought to put the direct URLs here as well for the latest 7.10.x and 7.11.x versions of the software. The .htaccess file relies on mod_rewrite (in apache) to carry out the following URL changes:
I know the feeling - I also like to tidy things up from time to time. I’d recommend getting it to work before clearing out anything, as if you clear everything out, you could plausibly break something and never know it? Once it’s working you can clear out something step by step. If something breaks then put it back.
You shouldn’t use composer update, it will take software dependencies past the versions that are tested with SuiteCRM. This can generate serious problems.
You should just use composer install --no-dev
And don’t worry about the deprecated messages, it’s true they need action, but it’s not clearing them out (that will leave holes in the software), it’s adapting the existing core code to require newer (or different) libraries. This is continuously being done, but it keeps needing more. It’s the natural flow of software growing old with time