Paul
-
Posts
6,728 -
Joined
-
Last visited
-
Days Won
841
Posts posted by Paul
-
-
This isn't a bad idea, disabling the editing of certain fields like names or company names could prevent accounts from being so easily sold to someone else. We'd probably use it internally ourselves.
- activa, Blesta Addons and Michael
-
3
-
Blesta 4.2 makes an attempt to determine the correct path to PHP under Settings > System > Automation. Not sure if this helps, but worth taking a look at what is displayed there if running 4.2+
-
I believe the client will have to do it. If that option was checked when they created their subscription, I believe they can do it within PayPal.. some steps listed at https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/manage_subscriptions/ You can check their subscription in your PayPal account also, and see if you have the option to change it, but I've only ever seen a cancel option.
-
7 minutes ago, austenite said:
Hey Paul,
It would be a request to add those features into the package tool within Blesta and then those values be passed on upon account creation within WHM. With blestas current implementation of this resellers can create an unlimited number of accounts that utilise unlimited space and bandwidth. So resellers aren't limited at at all, whilst the reseller themselves can be limited through a package on WHM, that only limits the reseller themselves and not their resold accounts.
The values that need to be passed are per my screenshot, the other permissions are managed through an ACL list. I'm happy to create a reseller account on my server for you to take a look at if you'd like.
I'm not much of a developer so wouldn't be able to provide any evidence of what specific things you'd need to tweak. Simply saying this as an end user of blesta.
So only the options in your screenshot? No others? I agree we should do this, but when I create the task I want it to be clearly defined.
-
I'm not totally sure I understand. Is this just a request to be able to set all of these reseller options on the Package in Blesta, if it's a reseller Package? When the reseller account is set, all these items are passed along? If so, does anyone have a list of all the options that should be included, or a screenshot in WHM where they would be set if created manually?
-
It's interesting that /dev/urandom is denied, most people that get an open_basedir error do not get one that references this path. You'll want to add this to your open_basedir path, or disable open_basedir.
-
If it keeps locking up, it's probably encountering an error and crashing. Since it's paid pending services being activated, look at your pending services.. most likely, some are failing to be activated, and possibly using a 3rd party module that is returning an error. Check also module log Tools > Logs > Module. Check also your file log (Settings > System > General > Log directory, open files in directory and look for errors at the same time)
-
23 hours ago, Blesta Addons said:
from my case i use, but the only issue i have that the select value is not in traslate mode like the field value . in your case, Please Select will not be translated when the client change language, instead of gender we can put it in language file and make it translatable .
Maybe the fields, like "Option Name" here should be able to be language definitions. If the fields could be translated, do you still think we should add Birthday and Gender? This would allow any fields to be added, and fully translatable. I think this is better than adding the fields into the core. Someone else will ask for SSN, hair color, or whether the person owns a dog, and custom client fields were intended to allow people to add anything they want.
-
24 minutes ago, sunrisepro said:
np. The cPanel module is connected; my new host imported all the cPanels for me (no change in cPanel names or anything). Is there anything else I need to do?
If they were imported properly, then no, you shouldn't have to do anything. You may want to edit a few to spot check them, and ensure they have a username set that matches their cPanel username. If they do, you should be good to go.
-
On 4/26/2018 at 6:53 AM, sunrisepro said:
I migrated my hosting to a new server. I just cPanel module settings to connect Blesta to WHM. It shows '2/20' accounts, which I'm not sure what it means (there are 20 cpanels total).
How do I connect each cpanel for automated suspension and such?
Sorry I didn't see this thread sooner. Did you take a look at https://docs.blesta.com/display/user/cPanel#cPanel-ImportingcPanelAccounts ? It describes how to add an existing cPanel account to Blesta. The main thing is that it's pointing to the right server and the username is correct. If so, Blesta should be able to suspend/unsuspend automatically, etc.
-
14 hours ago, activa said:
Adding them and make them disabled is better than they not exist at all. My custom case require gender field more than adress2 field .
Why doesn't a custom client field work for you? For language, you can add your own language definitions to the custom language file and use a definition here for the name instead.
-
On 5/6/2018 at 12:26 AM, furioussnail said:
The fact that many do it in one way doesn't mean it is right. Yes, there are techniques used to prevent brute force attacks or user escalation but can you foresee any vulnerabilities? Even yesterday Twitter asked users to reset their passwords... So, not sure Twitter is a good example.
Just because Twitter made a mistake with their logging, doesn't mean that they don't know what they are doing. Twitter has some of the brightest engineers in the world on their team, many of which I'm sure, would disagree with you. Still, how IPBoard operates is outside our control and you should always assume an attacker has your username.
-
I think you can just convert the fields to hidden, however first_name, last_name, email, username are required.
In /plugins/order/views/templates/wizard/signup.pdt for example (your path may vary depending on order form used) search for first_name, and starting there change $this->Form->fieldText to $this->Form->fieldHidden for each field you want to hide.. probably first_name, last_name, company, address1, address2, city, country, state, zip, phone, fax. For the required fields (first_name, last_name), you may want to just prefill some standard info like "Customer" or something.
I may have time to play around with and test this, and if I do I'll post code you can use, and update the docs so it may be helpful to others.
-
5 hours ago, wdfee said:
Any news on this, yet? I took a look into the subject https://dev.blesta.com/browse/CORE-2463 with subtasks - most unassigned and unresolved. So I'm from Germany and all of my clients are in the EU. If Blesta won't be compatible with the GDPR in two weeks, I have to quit blesta and use another software.
It's in progress, thank you for your patience. The first phase, to be included with version 4.3 ASAP, will have everything you need to make it easy to comply with any requests you may receive. If you receive any requests prior to our release of 4.3, let us know and we will help. It's still possible to comply, but is a little more manual.
-
I would suggest contacting IPBoard about any concern. Most organizations do not have secret usernames.. they force the use of email addresses, or display usernames publicly. Reddit, Twitter to name a couple allow you to login with your display name. I operate under the assumption that an attacker knows my username, but I can see how you'd want that to be secret. Nothing we can do about it though.
-
13 hours ago, Chris van der Westhuizen said:
Hi Paul, files left the building ? See your email box. I hope you will like my spiderweb compilation ?
Yes, it is very spiderwebby indeed. ? Fortunately the relationship notation can be changed from spiderweb to UML ?
I forwarded you Tyson's response to your questions.
-
3 minutes ago, Blesta Addons said:
We have only for php 5.4 and 5.6, and i think php 5.6 will word for php 7.0.
So there are 2 versions he can download? Maybe he downloaded the PHP 5.4 one. Yes, the ioncube encoder for PHP 5.6 should work for 7.0.
-
On 4/29/2018 at 1:43 PM, JAMMAN said:
What am I missing, there is no "Quarterly" option for payment in the new package setup that I see?
When creating a package, you can set multiple prices to cover whatever terms you want. When editing the package, click "Add Additional Price" under Pricing. Then for Term, enter 3, for Period select Month, and set your price. You just added a 3 month/Quarterly option.
-
-
7 hours ago, Blesta Addons said:
Hello Sir
normally any new service is activated instantly (max 5 minute after successful payment ) . if you have any trouble PM me or open a ticket .
I'm helping him setup his Blesta. Do you have a PHP 7.0 compatible version of xtreme_codes module? I get an ioncube error that it is for PHP 5.4, and need to be encoded for PHP 5.6 (which will work on PHP 5.6 and 7.0).
-
On 4/28/2018 at 8:25 PM, EMar said:
Thanks, I can't find /usr/local/apache/modsecurity-owasp-old/ in my Centos installation, using sftp as root.
That's weird since your error mentions the path /usr/local/apache/modsecurity-owasp-old/base_rules/modsecurity_crs_41_sql_injection_attacks.conf
locate injection_attacks.conf
Maybe you'll get a result? If you get a "database" error, unable to search..
yum install mlocate -y
updatedb &And try again after a few min.
-
2 minutes ago, Jonathan said:
That's pretty much my point for having the ability to completely disable it. As soon as it's there people can/will get offended. If it's not there, everyone is equal.
Maybe it can just be a write-in, I dunno.. but I agree, both DOB and gender fields disabled out of the box.
-
Also, separately, I don't know if we really want to get into the gender debate. ??
-
4 hours ago, Jonathan said:
If such fields were added to core as opposed to using custom fields it should also be possible to disable them completely as not everyone will want to use these fields or even allow customers to fill them in.
That's the thing.. which makes this 2 feature requests. New fields + ability to hide/disable fields. Right now you can set which are required fields, though First, Last, Email is always required, we'd have to add another option for whether to show the field at all. I think it'd be a good feature, people sure ask enough about removing fields, but it's two feature requests.
Vultr Module (Alpha)
in Extensions
Posted
This is likely out of date and the file attached to this thread has revisions. It'll be on our Github soon.
Regarding this issue you've found, what is the affect? Also, feel free to post any other issues in this thread and we'll take a look.