theme template with all the files to edit in it...

catfish

So, epesi-1.6.3 is a GREAT SCRIPT - AMAZING actually... but it is the biggest pain in the *yeah you guessed it* to edit it.

I suggest/request that ALL the php files point to their own html file that is in one folder labeled theme/s.

for example: wordpress files are easily accessible and easy to manage

- Core files and php stuff... (folder)
-- Login_0.php * calls html template file for displaying view

- Theme (folder)
-- Login_0.html * I can edit whatever I want on this page and easily add html and div. codes

Your categorization of files right now is driving me crazy, going around from file to file to end up not being able to easily edit files.

Right now, the login tpl is only called IF using demo mode...

SCRIPT OUT OF THE BOX: 9.8 stars

ABILITY TO EDIT: -3 stars

and even though it is a great script THE WAY YOU LIKE IT... there are at least a couple hundred thousand people that would appreciate the ability to edit your amazing CRM

Thanks for your time, and sorry to rant on my second post here... but I have already spent a few days tampering around with all your files to still feel lost at times, so I can only imagine how a "beginner" web designer feels when opening your sub directories

ajb

I suppose that this post is strictly related to this one.
🙂

So to clarify... every module in EPESI is responsible for its own view. So every template file is put in the module's directory.
If there is some generic module that is used to generate view, then it's the place where you should look for the html - Like RecordBrowser uses GenericBrowser to show tables.
Then every modules output has it's own place on the screen. For instance like a dashboard - every applet that you see is a applet method of a certain module, but in most cases those applets are a tabular view that in fact is a view generated by RB (that uses GB).

For me it's easy to find the right place - it's just a matter of understanding 🙂

I don't know what lead you to assume that login tpl is used only for demo mode :wink:

Regards,
Adam

catfish

This post did originate from the frustration built up over the other post :twisted: but I have also noticed that changes made to the Box_0.php and Login_0 .tpl files are not responsive.

I agree, if the script were to act how you mention it would be REALLY easy to modify things... however, I have had to make div tweaks with style codes to accomplish my tasks I have needed. For example, when editing /modules/Base/User/Login/Login_0.php I have entered and edited the theme files located in /modules/Base/User/Login/theme/default.tpl but it looks like that file is only called if the "demo" site is activated.

also, I am going to be using this script where collecting cached files is not acceptable, where can I disable the script from storing cached files? Thanks again for your quick responses 🙂

ajb

Indeed changes in modules/*/theme files are not visible. You have to make a themeup procedure. <epesi address>/admin/ -> 6. Rebuild common cache & default theme

With theme up all templates files of the installed modules are copied to the data directory - into data/Base_Theme/templates/default. You can edit them there, but if you'll change them in data/Base_Theme then you have to copy them into modules/*/theme directory to make it permanent over theme up procedure.

What do you mean by collecting cached files? Templates caching?

catfish

I see, I will have to tinker around with creating a new module and tpl... but this answer sort of answered my question about the cache system. I noticed that sometimes after making a change the change doesn't always take effect right away. When that happens the script I am using is usually caching files somewhere.

This is a very in depth and intriguing software/script... I enjoy learning it and seeing all that it has to offer.

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge