« Last post by datahell on April 20, 2024, 21:39:24 »
In the upcoming Elxis 5.5 the parameters of various extensions (modules, plugins, templates, etc) gets saved by default as JSON strings and not as newline separated text as up to Elxis 5.4. Elxis 5.5 is backwards compatible as it detects automatically the format of the string and you have no problem at all. However if in any third party extension you have developed you use to parse manually the parameters string you got from the database, you must check if the format is JSON or the old one before trying to parse the string. In this case post a reply below for instructions on how to parse the string.
Elxis 5.5+ JSON format (same parameters as above): {"width":"120","height":"45","colour":"red"}
Elxis saveS automatically the parameters when you edit a module, a plugin, etc. But if you ever need to save them manually in your extension the use the new methon toJSONString. I will post an example with backwards compatibility, so the code below works on any Elxis version (for a sample module): elxisLoader::loadFile('includes/libraries/elxis/parameters.class.php');
Note: Users will require to update all third party extensions that need update before updating to Elxis 5.5, because of Elxis 5.5 compatibility fixes. I have already released some updated extensions with Elxis 5.5 support.
« Last post by datahell on April 20, 2024, 21:28:42 »
1. Insert link. After you add a link, or anything from the toolbar, you must click anywhere inside the text area in order for your action to take effect. Then click save/apply. Is it working?
2. Upload and insert image. Don't go to the "Upload tab" go to the "Browse" tab. Select an existing image from media/images/ or upload an image in any folder you want by clicking on the plus (+) icon button on the top. After upload double click to insert it in the editor.
« Last post by datahell on April 20, 2024, 10:31:25 »
I am also a refugee, but from Mambo, long before Joomla existence. In Joomla's day 1, I decided not to go to that toxic, as you said, CMS, but build my own, Elxis (Actually Elxis borned before Joomla, on December 2005 and the first version was a modified version of Mambo). We kept naming (module, component, etc) almost as there were in Mambo and are in Joomla, but Elxis evolved and today it has its own framework and ecosystem. If you ever wonder how to do something in Elxis, think as a true developer, the CMS is there to help but doesn't limit you to follow the standard path. You can be yourself. Welcome to Elxis.
« Last post by cjstudio on April 20, 2024, 07:46:17 »
I think I understand it now. As I mentioned earlier, I'm coming from Joomla!, version 3 to be specific, and am one of the growing list of refugees from that project.
I was trying to understand how Elxis does things. It seems so easy - build a module, and either use AJAX to do a submit or otherwise code up a module with its own built-in form. This behavior effectively emulates what a Joomla plugin does - that is, it is called by an action based upon what process must fire at a certain point in the code execution. As I am also building a component, some of the component forms could likewise trigger actions on submit.
I am looking forward to digging in and having fun.... like way back in Mambo days.
And as a side note, thank you so much for your friendliness and help! I had gotten so used to the toxicity from that other CMS that it's going to take me a while to get used to it.
« Last post by datahell on April 19, 2024, 20:04:08 »
Τότε γράφεις το κείμενο στα Ελληνικά, αλλάζεις γλώσσα στα Αγγλικά και πατάς το εικονίδιο της μετάφρασης (σφαίρα). Δοκίμασε πρώτα με κάτι μικρό, πχ με έναν τίτλο. Συνιστώ το DeepL (απαιτεί τη δημιουργία ενός API - έχει δωρεάν και επί πληρωμή έκδοση). Όλα τα εργαλεία έχουν περιορισμούς στην δωρεάν τους έκδοση.
« Last post by panwine on April 18, 2024, 21:53:49 »
καλησπέρα η έκδοση ειναι η 5.4 από ελληνικά για αγγλικά με ενδιαφέρει ευχαριστώ για την απάντηση. παροχο ενοειται ενα απο αυτα DPPL GOOGLE FREE MYMEMORY /TRANSLATED
« Last post by datahell on April 18, 2024, 20:59:47 »
I always reply with detailed instructions
You only need a module with an AJAX call to user:ilogin. If the default login module is not suitable for you, you can see how it works and build your own. Modules are very easy to develop. I will guide you if you need help.
The module may also execute its own tasks, AJAX driven, in a very secure way. There are many such modules you can see as examples. Here is a starter tip:
AJAX calls from modules should be addressed to "ajax" page of component content. The URL is constructed like this (PHP): $elxis->makeURL('content:ajax', 'inner.php'); (returns something like https://example.com/inner.php/ajax - "content" is the default root for frontend so it is removed from the final URL)
When you request the above page you must pass a "f" variable which is the relative path to the file (a module file usually) you want to be included in order to execute further actions. Here are some sample variables (javascript):
« Last post by datahell on April 18, 2024, 18:35:14 »
After the module installation you will see on the top right corner of administration panel an @ symbol. Click it to open the module interface.
Manage recipients Click "New recipient". Add a name and at least one e-mail address (email2 and email3 are optional). On "Group" select "Other" and type a group name. This is to help you organize your contacts. The group can be anything you want. For example: Providers, Suppliers, Hosting customers, Friends, etc. You can optionally also add a note for this recipient. Click the Save button. Your recipient has been save.
If you want to edit or delete it do this: Click "New message". Select the recipient you want from the list. You will notice 2 links, one for editing and an other one to delete the selected recipient.
Send a message Click "New message". Select the recipient you want from the list. If you want type one more e-mail address in the "Send copy" field. It can be your own email too. The Send Copy email will be added to the email message as CC. Select a template from the list. The template controls the layout and content of the final email. Templates can have custom content and be totally different. Each template may have places to add custom content (like payment amount) and personalized content (like the name of the recipient). After you select the template you will notice a number of new fields to be displayed below which you must fill-in. These are the custom content of the template. You can also modify the email Subject been generated by the selected template. When ready click Send message to send the message to the recipient(s).
Manage templates The module comes with a default demo template in English language. You will find the templates under this folder:
modules/mod_admincontact/inc/templates/
Each template consists of 2 files having the same name but different extension, one html (the email content) and one php (contains custom fields, images and email default subject). The names can be anything. Give names that make sense. Example:
customer_en.php customer_en.html
You can create copies of the above for different languages and name them something relevant. Example:
customer_el.php customer_el.html
Do not modify the default demo template because you will loose your changes in a module update. Copy its files and rename them to create a new template instead.
The PHP file Must contain 3 variables with names $tpl_subject, $tpl_params and $tpl_images (follow the demo template example).
tpl_subject: This is the default email subject tpl_params: these are the custom parameters that existing in the template (optional) tpl_images: These are the embed images in template (optional). Images must exist in templates folder.
The actual content of the email is the contents of the HTML file. Inside it you will notice string like this {{AMOUNT}}. {{AMOUNT}} is a custom parameter. An other one can be {{WEIGHT}}. We define these parameters in the PHP file like this:
After you select that template in administration you will see 2 new fields labeled Payment amount and Weight in Kgr which you must fill in. The module will take whatever values you provide to these 2 fields and replaces all instances of {{AMOUNT}} and {{WEIGHT}} with the text provided.
There are also 3 standard parameters which you dont have to defined and you can use directly in your HTML template. These are:
{{NAME}} : Recipient name {{DATENOW}} : Current date (short date, year month day, as of Elxis DATE_FORMAT_2) {{DATETIMENOW}} : Current date-time (long date, year month day hours minutes, as of Elxis DATE_FORMAT_4)
There is also an other array ($tpl_images) where you define the images used in your email template (optional). The format of this array is similar to tpl_params. Example:
HTML skills are required to create a brand new email template. However you have solutions:
1. There are several sites on the internet that provide free and paid email html templates. You can download such templates to use them in module Admin Contact. Sample (free) such sites: Mail bakery, themezy, colorlib and many more (most require free subscription - not the ones I posted).
« Last post by cjstudio on April 18, 2024, 06:23:55 »
Hello again. I was away for a bit due to a family emergency.
I now understand that Elxis does not have a general "plugin engine" so to speak (i.e., like Joomla's JPlugin).
After reading what you've so graciously posted, and thank you for taking the time to provide such a detailed response, it looks like the best way to achieve what I want for my project is to use a combination of module and component coding (as this is going to be a fairly involved project). The module could contain custom forms that essentially provide the desired action as forms can be triggered via submission. I'll have to read up more on the URI system, as this does indeed look very useful.
And, because forms can be hidden, I could pass parameters if needed via hidden forms and Ajax.
Please let me know if there are any mistakes in my understanding. Thanks again!