Jump to content

EuroDomenii

Members
  • Posts

    13
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Thanks
    EuroDomenii reacted to Paul in Domain package group architecture   
    I've created this task https://dev.blesta.com/browse/CORE-4586
  2. Like
  3. Like
    EuroDomenii reacted to Michael in Blesta 4.6.x + integration with BlestaCMS Community Edition (Free)   
    So you would like to integrate Blesta into your theme but don't know how to? Why pay for expensive integrations when you have to relay on them replying in time and giving you updates when you need them when you can do it yourself. If you can't do it I highly recommend you use a third party integration company. I personally recommend ExpertIntegrations.com but you can use Blestaintegrations.com, etc.

    Today I will be using the theme Appy. It's a free theme if you KEEP the copyright otherwise you have to pay to have permission to do so.
    Meaning you are not allowed to remove footer credits for that you must purchase a License.
     
    Download the theme from: https://colorlib.com/wp/template/appy/
    Extract the files to your computer and create the folder on Blesta in
    /app/views/client/ In this tutorial we're calling it appy.
    You'll need to copy the files from the default bootstrap folder to the new one appy.
    After you want to upload the files from Appy to the custom theme folder you are creating.
    /css /fonts /images /js /style.css
    Next we need to add the images to the root of Blesta so the CMS can use them straight away. So simply copy the images folder to the root of blesta like so:


    Back to the theme let's rename it to Appy.
    In the folder:
    /app/views/client/appy/ Find the following:
    config.json with:
    { "version": "1.0.0", "name": "Bootstrap", "description": "Built on Bootstrap 3.1.", "authors": [ { "name": "Phillips Data, Inc.", "url": "http://www.blesta.com" } ], "require": { "blesta": ">=3.2.0" } } Rename the name to anything you like. I'm going with Appy. So mine looks like:
    { "version": "1.0.0", "name": "Appy", "description": "Built on Bootstrap 3.1.", "authors": [ { "name": "Phillips Data, Inc.", "url": "http://www.blesta.com" } ], "require": { "blesta": ">=3.2.0" } } Finally go to Blesta and enable the theme so we can start integrating the theme. Go to:
    Settings > Company > Look and Feel Click on Template on the left and click Appy (or your chosen name).

  4. Like
    EuroDomenii got a reaction from Michael in Domain Manager - We need your feedback on domains   
    Our company is an .Eu Accredited Registrar,  and the .Eu registry - EURid, offers discounted registrations for the first year. We pass this discount to our clients, so is very useful to have lower registration pricing and higher renewal pricing.  
  5. Like
    EuroDomenii got a reaction from Paul in Domain Manager - We need your feedback on domains   
    Our company is an .Eu Accredited Registrar,  and the .Eu registry - EURid, offers discounted registrations for the first year. We pass this discount to our clients, so is very useful to have lower registration pricing and higher renewal pricing.  
  6. Like
    EuroDomenii reacted to Blesta Addons in Domain Manager - We need your feedback on domains   
    Welcome back again ?
    in my opinion the renewal price is a good addition, sometimes you need to make a promo without offering promo code, this way you can offer promo for renewal or registering with a easy way. it left now the transfer price wit the same logic as renew price, the transfer price will be only used in order form as it happen only the first time of contract. after making a unified commands for domains modules will solve all other issues, after this two steps we can release our custom order form to the community. (used here https://nh.ma) we can't release it as we have some tweak in our modules and some core files .
     
  7. Like
    EuroDomenii reacted to Tyson in Changing admin urls with certains values determines not found behaviour for client logged in area   
    The admin route you have set conflicts with other routes in the system, which is why you encounter that behavior. We may be able to resolve that issue though, which we will look into shortly. Thanks!
  8. Like
    EuroDomenii got a reaction from activa in Changing admin urls with certains values determines not found behaviour for client logged in area   
    The "buggy" admin_urls  ( a,x,in) doesn't exist in blesta. Anyway, blesta should have a validation in place.
     
    There are pro and cons security throughobscurity.
     
     
    From my point of view, anyway I shall restrict by IP the admin url. I just love the idea of having one letter admin_url. It's fast and fun. 
     
  9. Like
    EuroDomenii reacted to Tyson in How To Get Order Number In Blesta   
    I think it's first important to understand the payment flow here. When a payment is made using a non-merchant gateway, the gateway is unaware of how the invoice it is intending to pay is created, or even if there is an invoice at all. You can make a payment using the non-merchant gateway to pay for nothing.
     
    In your case, however, you want to pay for an invoice created from an order in the order system using the Order plugin. This is a special case, and should be treated as such. Which means, you should not rely on this to always be true, and must setup logic to handle the cases where it is not.
     
    In your non-merchant gateway's class, you should have defined a buildProcess method. This method accepts, optionally, an array of invoice amounts as its third parameter. In that array is a list of IDs representing the invoices being paid. If you are paying an invoice on the order form, you should only have one invoice ID in the list. You need to take this invoice ID and find the associated order ID from the order system.
     
    Considering the order system is a plugin, it may not be installed for the company. You should check that it is first.
    Loader::loadModels($this, array("PluginManager")); $order_number = "N/A"; // Is the Order plugin installed? if ($this->PluginManager->isInstalled("order", Configure::get("Blesta.company_id"))) { ... } The Order plugin associates an invoice with the order, so you must find the correct order that matches the invoice ID you were given. However, the Order plugin does not provide a method to find an order by invoice, so you must write your own. First, make sure you have an invoice number.
    $invoice_id = null; if (isset($invoice_amounts[0])) { $invoice_id = $invoice_amounts[0]['id']; } Now you need to find the order number associated with the invoice. Since the Order plugin does not have a method for doing this, you can either 1) add a method for it to do it from the OrderOrders model by updating the source code yourself, or use the Record component to query the database for it manually. The later is more difficult as you will need to manually connect to the database by passing valid credentials yourself. See here for an example of someone that has. I will skip that part and simply assume the Record component is setup to perform a query.
    Loader::loadComponents($this, array("Record")); # # TODO: create a connection to the database # try { $order = $this->Record->select()->from("order_orders") ->where("invoice_id", "=", $invoice_id)->fetch(); if ($order) { $order_number = $order->order_number; } } catch (Exception $e) { // Unable to fetch the order number } Putting it all together now:
    Loader::loadModels($this, array("PluginManager")); Loader::loadComponents($this, array("Record")); $order_number = "N/A"; // Is the Order plugin installed? if ($this->PluginManager->isInstalled("order", Configure::get("Blesta.company_id"))) { // Do we have one invioce? $invoice_id = null; if (isset($invoice_amounts[0]) && count($invoice_amounts) === 1) { $invoice_id = $invoice_amounts[0]['id']; # # TODO: create a connection to the database so we can run a query # // Can we fetch an order for this invoice? try { $order = $this->Record->select()->from("order_orders") ->where("invoice_id", "=", $invoice_id)->fetch(); if ($order) { $order_number = $order->order_number; } } catch (Exception $e) { // Unable to fetch the order number } } } // Use the $order_number
  10. Like
    EuroDomenii reacted to Blesta Addons in Domain Manager - We need your feedback on domains   
    What is the Obstacle Now in Domains? in reality the obstacles are now :
    - Multi Price System, This can be fixed with more price fields like Renewal Price, we add more fields , Transfer Price, Restore Price.
    - Better Domain Management, this also can be fixed by adding the functions to the actual modules .
    - Unification Commands, this also can be done by actualizing the actual modules.
    - Privacy, Forwarding & other addons prices, this can be implemented with the actual  system by addons, we need just to tweak the actual modules to support this addons
    - if we want to distinct with domains modules and other modules we can add a new entry in modules to define is a domain module or not (true/false) or something like the order type definition.
    For me what Blesta need is enhancing the actual system  and not reinventing a whole system for domains.  now we have waited years to only hear a something from blesta, creating another system will take other 2 or 3 years, and the quick solution and the simple is to extend the actual exist mechanism to support new features .
  11. Like
    EuroDomenii reacted to Paul in Domain Manager - We need your feedback on domains   
    The goal is to remain backwards compatible, so far it's looking like that will be possible. Meaning that existing registrar modules should continue to work, and it shouldn't break when installing the domain manager. However, the domain manager may not be able to recognize pre-existing domain packages and take control over them. A way of conversion may be required to take full advantage of the domain manager with existing domains unless starting fresh for domains going forward.
  12. Like
    EuroDomenii reacted to Paul in Domain Manager - We need your feedback on domains   
    The renew price option in 4.6 is one of the core updates required for the domain manager, and can be used now to support a separate new and renew price for domains in the current system. A separate transfer price and better support for domains is coming. While I don't have an ETA yet, we have been making progress. I know that it's highly requested, and much needed, and our 4.6 release puts us 1 step closer in terms of underlying core functionality to support the domain manager.
  13. Like
    EuroDomenii reacted to Blesta Addons in [Module] Epp Registrar   
    The module is open source format .
×
×
  • Create New...