Leaderboard

It's becoming more and more important that we get The Marketplace finished up. Being able to install and upgrade extensions directly from Blesta, as well as browsing all extensions from inside Blesta or the marketplace website will make things easy. It will also have rating and review options.

Hi, Blesta only has been translated to my language for 13% so I am eager to help, I translated other solutions so I thought it would be again using a code editor and downloading the language files straight on the server, zipping them and uploading them somewhere, However there seems to be an entire blesta translation project going on; nice idea! However, it's taking me several times as long as editing straight in the files because the page has to load after each sentence/word. My question: - If I translate the language files via my editor, can I somehow upload them into the translate project for others to improve? - Is it possible to get 20/30 sentences/words shown at the same time? I really wanna help translate blesta but I find this way very time consuming and not very productive...

You say that but they bought HostGator, destroyed that reputation, they bought BlueHost, well you can just search BlueHost+Downtime to find out that story. I could continue but every company EIG has bought has been screwed over because they are just made of money. Not hosting industry knowledge.

We are talking here about currency that are not supported by some gateways . let imagine you have a company in a country that thier currency is not supported by paypal !!! how you can accept payment with paypal ? the only one solution is to add a conversion proccessor inside the system that convert a NO-SUPPORTED currecny to a supported one like USD . another more realistic case , a client that select XXX as default currency . when the invoice are generated with that currency , making payment with no supported gateway is not possible in blesta system . to understand me well , 1- add a new currency that are not in the supported corrency in paypal . 2- affect this currency to a client . 3- generate a invocie for this cleint with that corrency . 4- show me now how you can pay it with paypal . the worst thing now in v3 , that we should add all the world's currency to the gateways , and add the conversion inthe gateway. in v2.5 it was a simple option named multi-currency , when we disable it , all the active gateways appear to the client when he want to pay . now is impossible . IF BLESTA stuff didn't se any benifict from adding a conversion rate in the gateways for no supportred currency . make as a option that let the gateways appear to all cleints , whithout checking the currency in the cleints profile .

I'll showcase the winning theme on the new Licensecart Blesta page: https://licensecart.com/beta/blesta-monthly to help show it off for you

This is completely irrelevant. If the CC number field is sent by your webserver, it can be compromised regardless of where you load stripe.js from if your server is vulnerable. The point Paul is making is that your webserver is serving content to the client for a page that requests credit card information. As long as that is the case you are at risk if your server is vulnerable. This is why it is inevitable that stripe.js and other work-arounds will be squashed by PCI compliance.

From that site: Stripe.js is not used, nor is Checkout. The payment information is not transmitted directly to Stripe's servers, but it is transmitted indirectly to them through your servers instead. This has the consequence that your servers are the ones needing quarterly security testing. And you need to be able to answer "yes" to at least all the questions on: https://www.pcisecuritystandards.org/documents/pci_saq_c_v2.doc (and if you take the definition of "storing card holder data" literally these: https://www.pcisecuritystandards.org/documents/pci_saq_d_v2.doc ) Note that if you are processing a low number of transactions, compliance validation is not required, meaning your credit card processor is not required to ask you to submit proof that you actually did the testing or completed the SAQ. You still have to be in compliance though, meaning you can get into trouble if there is an incident, and it turns out you "forgot" to do them.