evolvewh
-
Posts
1,007 -
Joined
-
Last visited
-
Days Won
9
Posts posted by evolvewh
-
-
44 minutes ago, Tyson said:
The Process Service Renewals task says it has completed too? The cron log is missing an end date for that task, so it is either still running (unlikely) or has failed to complete (e.g. encountered a php error). You should be able to clear the task lock by going to the Settings > Company > Automation page, scrolling down to the Process Service Renewals task and clicking the Clear Task Lock link, assuming that link is available for the task, which I think it should be based on your description. Then you may want to run the cron manually from the Settings > System > Automation page so that the output is displayed in your browser and you can check whether an error occurs during that task's execution.
Tyson thanks for the help. I've attached a screenshot of the task under Settings > System > Automation and there's no way to 'Clear Task Lock'. When I ran cron manually earlier, the output was that everything ran just fine.
-
54 minutes ago, Paul said:
It really depends how Authorize.net has designed it. Some gateways (like PayPal, and other non-merchant gateways) make an IPN call back to Blesta with status changes. Merchant gateways like Authorize.net don't do that, or typically even have that ability, though it's possible some might. I'm just speculating, but my guess is that Authorize.net would want Blesta to periodically check the status of the transaction.. so this would be initiated on our end, and not their end. There is no mechanism built into the merchant gateway system to make automatic API calls to check the status of transactions, so *if* Authorize.net supports this, it would require a change both to the merchant gateway system and the gateway module.
If it could be implemented, I think a lot of users would benefit from this.
-
There are one or more cron tasks that have been executing for more than 60 minute so I ran cron manually hoping that would do the trick but it didn't. Process Service Renewals is the task stuck and should run every 5 minutes but hasn't for almost 3 hours now. I checked the logs and they say every task is completing. How can that be?
Blesta v. 4.2.1 and running php7
How can I get this resolved?
-
On 2/12/2018 at 11:14 AM, Tyson said:
Based on the response from Authorize.net, there should be a pending transaction created in Blesta for it. Since you have to take manual action in Authorize.net to accept/decline the payment, you'll need to take manual action in Blesta to do the same since Authorize.net does not make a callback to Blesta to allow the state to be transitioned after you accept it in their system.
Is this something that a developer and/or Blesta could add or is it something that's isolated to Authorize.net and what they're capable of providing Blesta with?
-
Or are some of your clients receiving them and others have the setting turned off within their client profile?
-
16 hours ago, rebus9 said:
I thought it was...... but when I added additional contacts to the account (contact type = billing) those contacts still do not receive payment receipt emails. Only the primary email address in the account-info section gets a copy.
But the opposite is true of new invoices. When I created a new invoice, the secondary "billing" contact got the invoice but not the account owner.
1st need: I need all contacts-- primary account owner plus any additional "billing" contacts, to all get a copy of any emails sent related to billing (invoices, receipts, late notices, etc.)2nd need: I also want our in-house accounts team to get a copy of all emails auto-generated by the system (receipts, invoices, etc.). VERY IMPORTANT. Our current system does this (it was a one-click global option) and we use it for sanity checking and verification. We don't want any emails from the system going to clients without a BCC going to our accounts team, so we know exactly what our customers are receiving. (We've caught errors this way.)
.... other than that, this seems to be a pretty nice product.I don't remember for sure but you may have to 'enable login' for them to receive these notices but hopefully someone else can clarify that.
For your 2nd need, you can go to 'my info' in the upper right corner when each admin is logged in and check the boxes under the 'Notices' tabs for the ones you want to receive.
-
3 hours ago, rebus9 said:
Our legacy billing system supports 2 email addresses per account, which is extremely useful. Many of our high-line clients have more than 1 person responsible for accounts payable-- or in some cases, the owner wants CC'd on all billing related correspondence sent to their A/P department.
Put in perspective, more than half of our clients have 2 billing email addresses tied to their account.
Is there a way to associate more than 1 email address per account?This is what you're looking for I believe: https://docs.blesta.com/display/user/Company+>+General#Company>General-ContactTypes
-
11 hours ago, Tyson said:
I've created CORE-2600 to look into that issue. It's extra interesting because a deprecated feature should still work. I'm sad their API removes functionality.
It's because of the major policy change from December 2016.
-
43 minutes ago, Blesta Addons said:
Yes, is true, just overwrite the core files with our files and you are done, when you want to switch again to the core module, just delete our files and upload core files, is easy ...
Sounds great. I just made payment and I'm waiting for the service to activate.
-
3 hours ago, activa said:
The logicboxes use a old function . I suggest using logicboxes reloaded from BA it has all fixed with domain forwarding and dns management .
The important this you dont need to install it and change package, just overwrite the core logicboxes file with it and you are fine.
This doesn't create any new tables and uses the same structure that the core module uses? That would be great if this is true.
-
-
This was the Output for the log and it happens on the admin side as well.
https://httpapi.com/api/contacts/modify.json
{"status":"ERROR","message":"Feature deprecated. Please refer to KB link"}I am not certain but I think is because the module does not support the new procedures put in place December 2016 by ICANN
-
A client is trying to update their Whois information in the portal and they receive this error: Feature deprecated. Please refer to KB link
Blesta is up to date and it's the standard logicboxes module.
Can anyone help with this?
-
On 2/2/2018 at 7:33 AM, viablethought said:
Hello -
When Accounts are created, typically the "business owner" is the primary Account Contact, however more often I am adding additional Contacts to the account for their Support Personnel and every time a response is submitted to a Ticket, the Primary Account Holder also gets an email. Is there a way to have it where if there is more then one Contact on the account, you can designate who Ticket Responses go to? I thought they only went back to the person who submitted the ticket but it was brought to me attention that the Primary Account Holder gets them as well.
Maybe this needs to be a Feature Request for the Support Manager Plugin?
Thanks in advance.As of right now, it's not possible. The Support Plugin is very light right now and really only covers the basics.
-
On 2/5/2018 at 2:13 PM, Tyson said:
What's in your gateway log regarding that transaction? My guess is Authorize.net responded to Blesta's payment request with a failure of some kind, so there wouldn't be any automatic follow-up to accept the payment later. Manually paying the invoice would be required at that point.
Input:
https://secure.authorize.net/gateway/transact.dll
a:22:{s:6:"x_type";s:12:"AUTH_CAPTURE";s:8:"x_amount";s:5:"70.00";s:10:"x_card_num";s:16:"xxxxxxxxxxxxxxxx";s:10:"x_exp_date";s:4:"xxxx";s:11:"x_card_code";N;s:8:"x_method";s:2:"CC";s:12:"x_first_name";s:4:"XXX";s:11:"x_last_name";s:5:"XXX";s:9:"x_address";s:19:"XXX XXXX";s:6:"x_city";s:7:"XXX";s:7:"x_state";s:2:"XX;s:5:"x_zip";s:5:"XXXXX";s:9:"x_country";s:2:"US";s:15:"x_currency_code";s:3:"USD";s:13:"x_invoice_num";i:XXXX;s:7:"x_login";s:11:"xxxxxxxGNHq";s:10:"x_tran_key";s:16:"xxxxxxxxxxxxxxxx";s:12:"x_delim_data";s:4:"TRUE";s:12:"x_delim_char";s:1:"|";s:12:"x_encap_char";s:0:"";s:16:"x_relay_response";s:5:"FALSE";s:9:"x_version";s:3:"3.1";}Output:
https://secure.authorize.net/gateway/transact.dll
4|1|253|Your order has been received. Thank you for your business!|046973|A|60935395890|2150||70.00|CC|||XXXX|XXXX||XXXXXXX|XXXXXX|XX|XXXXX|US|||||||||||||||||82F2D58FDA84B02FF336A699C39D61E3|||||||||||||XXXX3924|MasterCard|||||||||||||||||We have had to manually record the payment each time after accepting the charge through authorize.net
-
2 hours ago, BlestaStore said:
but with a pre-order you pay a retail shop, but with this people paid on a crowdfunded with all funds going even if they didn't meet the target. If I pre-ordered a game with Argos (uk shop) I'm protected by the UK laws and regulations but if the shop closed down and into administration I could lose everything.
I want to point out that @cyandark originally said he would refund all money if the target amount was not met and it never was met. He just 'said' he was still going to develop the extension and to this date hasn't.
-
20 minutes ago, BlestaStore said:
That's the issue of donating, to donate you are essentially giving money to help it. If you bought it you would be protected by the money back guarantee / PayPal. But there's been no movement, no updates, no previews so I'm just watching and thinking shall we mark it as broken to alert others that the module is un-useable in it's current form.
It was definitely broken and I would not advise anyone installing it now. This is going to set a precedence to not support any Blesta developers at this rate. Sad
-
1 hour ago, BlestaStore said:
I wouldn't get your hopes up if it continues I may have to mark the thread as broken module as the old one apparently doesn't work and the new one isn't coming.
If the new one truly is not coming, he will need to refund all of us who donated.
-
1 hour ago, BlestaStore said:
You can disable it telling it's correct but it does that to stop brute forcing. eg: I hacked your email account, and I know you have an account so I keep trying everything until it goes to your email address.
Disable it: /config/blesta.php
find:
// Default password reset value. Set to true for improved security, false for more accurate error reporting Configure::set('Blesta.default_password_reset_value', true);change it to false.
Thanks Michael. We may just edit the error message instead of compromising sercurity this way.
-
15 minutes ago, MineHarvest66 said:
While Blesta need to up their improvements this is actually not one of them. The reason why this is the case is because it's to "spoil" exploiters from breaching clients' accounts. If they "think" that their entry "worked" then they will be less likely to keep on trying.
It's kinda like cities having empty police cars, plain and simple but tends to work.
I can understand that which means they should implement an IP block. We get way too many support tickets about this and live chats with frustrated customers. There has to be somewhere to 'meet in the middle' and figure out a bettwork workable solution.
-
16 hours ago, espservices said:
Hi,
I'm new here and looking forward to start using Blesta. Domains are not my main business.. but a very important part. Can please someone from Blesta team tell if they are working on this? If yes, any kind of timeframe?
Thanks
The last response I got was basically 'we have a lot of work to do but we should have something available by the end of the year'.
-
Right now, if someone leaves the username field blank or enters an email address that does not exist, Blesta still says 'A confirmation email has been sent to the address on record.' when in fact, nothing is ever going to be sent to them. I'd like to request that Blesta validates what is entered and if it's blank, display a message saying 'Please enter a valid username' or if the email address does not exist in the system, say 'There is no match in our system for the email address you entered' or something along these lines.
-
We have the fraud tools enabled with authorize.net and we've had a transaction come through that was flagged for our review. After being accepted, it looks like there is no communication between authorize.net and blesta to either finish processing the payment or to void it. Is this true? I am thinking that we need to manually 'pay' this invoice after accepting the charge within authorize.net
-
Cron Task Stuck
in Support
Posted
Hi. Only Logicboxes Reloaded from your company.