velaware

Anyone know when 3.1 is going to be released?

Yeah but waiting until then doesn't help me now lol

So, Blesta v3 took out the "email clients" feature where you could send out an email to all of the clients at once (which I wish they'd bring that back...). Is there an alternative to doing this right now besides going to each client's profile and clicking "send email" or something?

Sorry on that, lol. I switched to the beta PayPal update so the UI is a lot different than the normal/standard/live one. But happy you found it!

Sorry for the quick double post but it seems to have been fixed after I updated the IPN information to send IPN messages and changed the URL to the path of Blesta (https://www.anzensolutions.com/accounts/ in my case). I apologize. I did have to manually resend all of the IPNs though that were marked as disabled. To do this go to Settings -> My selling tools (in PayPal). Click on "Update" on the right side next to the Instant Payment Notifications section. Click on the "IPN History page" link near the top of the page that pops up. Then select each one that is marked as "Disabled" then click "Resend selected". It may take a few minutes but now my invoices are being marked as paid. <3

Yes, IPN is enabled in PayPal but is set to a testing address. There's no information in Blesta as to what to set it to. They have been from Blesta 2.5 so far from what I can tell, with one being a subscription payment so its not displaying any specific invoice information.

Not to bust your bubble but the ISPConfig API is horrid and is in dire need of reworking. I had the same idea for Blesta 2.5 when I got it but after I dove into it I realized it wasn't worth it. Now, Blesta 3 has a hell of a better plugin architecture which makes it easier and more pleasant to work with, but the ISPConfig API is still leaving a lot to be desired. You can do a lot with it, don't get me wrong. But you're going to run into a lot of issues mostly due to poor documentation and even poorer code writing that the ISPConfig team has done with their product. I literally had to read through each line to see what was needed and where.

I've noticed that none of the invoices have been marked as paid (when I received payment late last week and early this week) via PayPal. I can't find no errors in the Tools->Logs area, and the transactions tab in that area shows absolutely nothing. Running Blesta 3.0.3 (3.0.4 doesn't seem to address any of these issues). Anyone have an idea as to why? PHP Info

I've got 3.0.3 installed. I've set up a rewrite rule to remedy this for now but I don't want to have to keep it in because of a bug, heh.

Is there a guide or something on what PDT files do what and how to theme it to your website? I'd like to integrate Blesta more deeply into my site but to do that I'd need to edit these files.

Side note: other places where it's used (i.e.: portal login, "login as client" for admin, etc...) are fine, its just the late notice email template that seems to be screwing up.

I'm noticing that when invoices are sent the {client_url} isn't set properly and am curious where Blesta gets this information when it goes to render invoices? I.e.: my Blesta install is at https://www.anzensolutions.com/accounts/ but instead the "Pay Now" link is pointing to https://www.anzensolutions.com/client/... (where it should be https://www.anzensolutions.com/accounts/client/...).

Personally this is why I love PostgreSQL. In MySQL you have to create a function to cascade/delete all data owned by a specific user when you delete that record. In PostgreSQL its there by default. I.e.: There's 5 records in invoices tied to user ID 1405. You delete the user 1405 itself, PostgreSQL will automatically know to delete those records under invoices as well (the power of true foreign keys).

The Smart Search feature, at least from what I've found, doesn't search through logs. It'd be nice if we could browse through logs as well (i.e.: to look up events that happened at a given time).

Nah lol I wish though. It gets annoying having to add a late fee to each invoice. It'd also be nice if it went along side the payment notices for those who have it set to email after the due date. Not sure if this is really logically feasible but would be nice.

It'd be nice to set a late fee per package or something for when an invoice isn't paid by the due date. I have to manually do it now and I remember in 2.5 it was a pain to write a cron script to do it for me.

Another option is to have the "View" link for the invoices turn it into a HTML-ified version of the PDF, and offer a link saying "Download PDF Version" near the top or something. Similar to what WHMCS does.

Describe the issue you're experiencing: When traffic is forwarded via proxy the user's IP is not fetched Provide detailed steps necessary to reproduce the issue.: This is provided at the end List any generated errors. (The "Oh Noes" error pages are very helpful.) None but is a flaw in a few ways (audit, security, etc...) Include the URL the error occurred on, relative to the installation path, ie "/admin/login". Not really sure how to address this Attach screenshots. See attached. Include your configuration settings, i.e. OS, version of Blesta, PHP & MySQL. Blesta 3.0.3, PHP 5.4.9, MySQL 5.5.32 So, here's the thing. I run a KVM which allows me to set up my own little containers/virtual machines. To get web traffic to and fro easily I have Nginx sitting on the host and it proxies traffic to the appropriate private IP and port (see config further down). When Blesta goes to log an IP of any sort, its a private IP due to this (either 127.0.0.1 [which I got in a "forgot password" email] or 10.0.3.1 [which is my virtual container's gateway IP]). As stated, this is an issue for audit, security and most likely other reasons. Here is my Nginx config for the appropriate information: server { listen 443; location / { proxy_set_header X-Forwarded-Proto https; add_header Front-End-Https on; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass https://10.0.3.3:443; } } From my experience in dealing with detecting proxies, checking the headers for "X-Forwarded-For" is most common, and you can also check for "X-Real-IP" as well. An interesting bit though with Nginx is that it doesn't set the real IP in HTTP_X_REAL_IP. See here: HTTP_X_REAL_IP: 10.0.3.1 HTTP_X_FORWARDED_FOR: 67.149.33.xxx, 10.0.3.1 I know it's not a sure fire way of fixing this issue but maybe check for more proxy headers or something? While I know my set up is technically custom (i.e.: specifying the headers nginx should pass), there could also be an option set in Blesta as to which header to check for, polling from a list of $_SERVER items or making it manually entered.

Right, but should I do that before or after assigning the key to the new install?

How would I go about re-issuing the key? Should I change the key in the new install first then update it via the Philips Data side, or do it on the PD side first then update the key in my install?

Are the ones from the selector stored in the table "themes"? If so then couldn't I export the data and just reimport it on the clean install? Or is the data's encryption specific to an install?

They're from the color selector

Is there a way to back up the themes at least since that's the most important of all data I need?

In a way it does, but I already imported the data once, but I've had new invoices, tickets, etc... created since then so I don't know if the import would fail due to the data already existing or if it'd just continue on.

So, here's the story. When v3.0.0 was released I plopped it onto a live environment that wasn't seeing the day of light. I got everything installed, imported all of my data from 2.5.4 from that point and was happy. Since then I've made various changes (i.e.: added templates, edited some settings, etc...). However, I still have 2.5.4 installed where it was needed as I couldn't migrate everyone over just yet. What I'm wondering is if there's a way to import the data again from 2.5.4 into 3.0.0 without causing any conflicts, or what I would have to do? I really don't want to have to re-install 3.0 because of the work I made, but if its the only option I will.