ctalkington

In regards to hostname, this is something I've manually fixed before. Instead of removing the IP, I just added another field and changed a few outputs to use it and it can be referenced in emails as well. I borrowed a lot of the naming/logic from cPanel module. Here's a gist showing the changes made (replace + with / for filenames): https://gist.github.com/ctalkington/e72ecefaeb1cd3eec73905e411dba89c/

any chance of getting this an ID assigned for tracking? seems its come up a few times.

I received a cron error when payment reminders attempted to send. PHP Fatal error: Call to a member function deliverInvoices() on a non-object in /app/controllers/cron.php on line 858 I've manually patched this by placing this at 811: if (!isset($this->InvoiceDelivery)) { $this->components(array("InvoiceDelivery")); } Blesta 3.6.0-b1 PHP 5.6.13

wanted to bump this to see if it can be addressed in next version.

The following page mentions "The coupon may be set automatically when added to a URL at /order/main/ or /order/config/ using the parameter coupon." http://docs.blesta.com/display/user/Order+System#OrderSystem-LinkingtoanOrderFormtoIncludeaCoupon However, when using the wizard list the "/order/config/" aspect doesn't work (ie /order/config/index/web-hosting/?group_id=2&pricing_id=13&coupon=10off) will take you to the product but won't actually apply the coupon. I found that adding the preAction block found in "plugins/order/controllers/main.php" to "/plugins/order/controllers/config.php" that it applies the coupon correctly. Is there a reason why this logic wasn't added originally?

im not sure if the guys have gotten much in build processes like grunt but there is a nice task for this: https://www.npmjs.org/package/grunt-cssjanus WordPress community has adopted this heavily recently.

any possibility of this getting a ticket and version set for correcting this.

im not sure there is much to do besides maybe update the version mapping? there really weren't any removals from looks of changes posted. blesta doesnt deal with any of the hosting values and leaves that up to the plan id. the only other thing that might be nice is to use the new convert reseller to customer command for 12.0.

technically, this could almost be done with an adjustment to the contact system to add a type for previous primary contacts (no login, admin only listing). then store contact id with invoice. the cost is most likely minor since youd specify the exact ids you want as part of invoice row.

got an email? i can send through some info.

Its a homebrew combo of base conversion, ord, and character shifting (two passes). I had to go the decoding route to track this down cause I don't feel my data should be locked in the way HB has made it. This was fine for my purposes but it makes it a challenging to release due to copyrights.

nice! what id really like to see is support for the email reselling side of things. once you get past 50 domains hosted, it gets a bit fun to keep it all straight. i do think a email module will be my focus after migration from HostBill.

yah, i've been working on an internal HB importer for myself on and off for the past few months and thats picking and choosing the parts I really need. had fun dealing with decoding the passwords too

I feel that the plesk component should treat these two a bit more uniquely in a few places: a ) id storage: should store the reseller id and not the webspace id of primary domain (more below) b ) stats: for resellers it should really pull from the reseller info api and show things like accounts provisioned vs avail, total space used vs allocated in recent versions 11.5/12, cant confirm previous, plesk allows the webspaces under a reseller directly to have a service plan or custom limits just like any other webspace. this makes it a misleading figure to show in blesta specially when it comes to space and such.

i agree its def a tricky road to go down. i just dont see the groups being useful if provisioning requires hacking of plesk IDs to work.

There's a rendering issue with the coupons expanded info where it doesn't properly render the currency code html.

initial patch here: https://gist.github.com/ctalkington/7f31f81cb14a5251143b

i've patched this on my install. https://gist.github.com/ctalkington/fb28c2a1d47d0c3ead83/revisions

This view seems to be missing a status filter for "refunded" status.

its also worth mentioning the language for "Plesk.!error.ip_address.valid" isn't set either.

This component has a few issues when it comes to hostname and ip address. a ) ip_address allows for IPs and Hostnames but its used in the module in places only IPs are accepted. ( see plesk.php L#433 L#443 etc) b ) the auto login form submits to the IP as thats all it knows. this causes SSL warns which can hurt client trust. I suggest that a host_name field be added like cpanel has and the ip_address be validated as IP only.

I was playing around with a few ways of configuring Plesk in Blesta. I noticed that the component allows for groups but requires plan IDs to be the same on all the servers in the group which is restrictive. specially when servers can be deployed by different technicians and at varying times. this means groups wont work unless you've: a ) added all the plans in same order on servers (and nothing more) b ) manually adjusted all the ids in the database (without upsetting plesk in the process)

I've been working on an import from another billing system which doesn't use the webspace id. I believe the component should expose a function that allows for looking up a webspace id by domain (connecting to the package server). This helper would allow services to have stats working after import vs having to manually update the IDs for what could be hundreds of domains. As said billing system didn't have an importer yet, I've made my own mapping by running sql on each plesk instance and storing in the plesk config map.

Unless I'm missing something here, when managing a service the prices listed are misleading. First off, if a recurring coupon was applied to the service, it doesn't appear to be listed anywhere for client. Then its not expressly clear to the client if any options are inclusive or exclusive of the recurring amount. I would suggest some kind of area that shows what the renewal price would be figuring in base service price (or override price), options / addons, and coupons.Showing the applied coupon code would be good too. As a side note, looking around in backend, recurring coupons dont appear to show up in the manage service admin either. This seems like a pretty big oversight to me. (looks like CORE-1066 might handle this part?)

thanks for tracking it.