BackendPro 0.6.1

[eluser]alainm[/eluser]
See that is exactly what i'm looking for.. thx

[eluser]shinokada[/eluser]
When I made my application with BEP, I had to modify/add code to BEP files.

I read that BEP v1.0 will not be backward-compatible.
That's fine for me even though I have to rewrite the code for v1.0.

However I am wondering if the future version of BEP v1.0, v1.1, v1.2, ... will have ability to upgrade by just overwrite the core BEP.

That will be nice to have.

[eluser]adamp1[/eluser]
Yes this will be a core idea I am hoping to implement. It won't be just click a button and it will upgrade because you may have added some of your own code to BackendPro files. But if you don't edit BackendPro files it should be just click a button.

You will be able to upgrade from 0.6.1 but it will be a manual process.

[eluser]shinokada[/eluser]
My majority of codes are contained in modules.
However I found that I modified the following BEP files for my application.

Code:

systems/apprication/language/english/backendpro_lang.php
system/apprication/views/admin/menu.php
system/application/config/autoload.php
        modules/site/config/bep_assets.php
system/application/config/backendpro.php
        modules/auth/language/english/userlib_lang.php
system/application/controllers/admin/settings.php
        modules/preferences/language/english/preferences_lang.php
etc.

I think I should create my own language files in stead of adding to Bep lang files, so that when I update the future BEP, it will avoid overwriting the file.
I can avoid the problem with autoload.php by loading files wherever necessary.

Now I'd like to ask expert's opinions about bep-assets.php, config/backendpro.php and admin/settings.php

What is the best way to avoid overwriting when I update the future version of BEP?

Is it a good idea to make my-assets.php, config/my_additional_bep_file.php and admin/my_settings.php and then loading these files together with other lang files in system/application/libraries/my_new_controller.php?

This will create the complete separation from the core BEP.

[eluser]adamp1[/eluser]
Yes that would work. Tbh this is the hardest part of the upgrade process 2 options going forward I think:

1) Remove config files and store all values in class. This would mean the user can create a config file which would over-write the default values saved in the class.

2) Have the idea of a MY_bep_assets.php etc config file as you mentioned. This has the added benefit of keeping all config settings in config files rather than in the class.

Don't know which one I would do tbh atm.

[eluser]shinokada[/eluser]
I am a bit stack with the backendpro_lang file.

I am trying to separate my codes from BEP so that it will be easier for future BEP release upgrade.

I extended Admin_Controller in order to load necessary libraries, helpers and lang files instead of autoloading them.

Let's call it Shop_Admin_Controller.

So I use it for all my module controllers, not in BEP controllers.

I used to have the followings which used for my back-end menu in backendpro_lang.

Now in order to separate them I created application/english/shop_lang.php and load it in Shop_Admin_Controller. (so that I can overwrite backendpro_lang)

Now as I mentioned I don't extend Bep controllers(access_control etc.) with my new Shop_Admin_Controller, all the language lines don't come out in the Bep controllers.

There are two solutions I can think of but both of them defeat the purpose of separating files for upgrade.

1.
I could load this new lang file in Admin_Controller.

2.
Extend all BEP controllers with my new controller, Shop_Admin_Controller.

Is there any better way to avoid this kind of problem?

Suggestions will be appreciated.

Thanks in advance.

Code:

* All Main Controller Names and menu items */
$lang['backendpro_general'] = 'General';
$lang['backendpro_admins'] = 'Admins';
$lang['backendpro_calendar'] = 'Calendar';
$lang['backendpro_categories'] = 'Categories';
$lang['backendpro_customers'] = 'Customers';
$lang['backendpro_menus'] = 'Menus';
...


/* Shoping cart */
$lang['general_login'] = 'Log in';
$lang['general_logout'] = 'Log out';
$lang['general_not_logged_in'] = 'You are not logged in';
$lang['general_cart'] = 'Cart';
...

etc

[eluser]elektron[/eluser]

As I am quite new to codeigniter and BackEndPro I have a lot of questions,
I have translated language files but I don't know where to set-up to be read by BAP. So I overwritten english files with mine. And it's working but this is NOT the correct way.
- What config file contains lang/idiom file to be replaced.
I have opened in all language folders aside english additional croatian folder with same files translated.
- I don't understand where to start once the user(not administrator) have logged-in where to create it's CP and how?

I would like to have possibility for users to edit their profile, send and receive kind of tiket, upload image/doc files and have represented one table with payment transactions.

Great work

[eluser]shinokada[/eluser]
RE: How to take out application folder out of system folder?

I changed config.php

Code:

$config['index_page'] = "";

And I have this in index.php

Code:

$application_folder = "application";

I also added .htaccess

Code:

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond $1 !^(index\.php|assets|robots\.txt)
RewriteRule ^(.*)$ /ci_test/index.php/$1 [L]

I took out the application folder out of the system folder without success.

When I visit http://127.0.0.1/ci_test/auth, it will give an error.

Code:

Unable to load the requested class: status

Can I take out application folder out of system folder?

If so, how?

Thanks in advance for your help.

[eluser]elektron[/eluser]


I don't understand very well the codeigniter but I give a try.
I wish to have an flash intro on my site.
I have changed this;

Code:

File: /web/CodeIgniter_1.7.2/modules/site/config/bep_assets.php

// mojWEB Flash JS
$config['asset'][] = array('file'=>'swfobject.js', 'needs'=>'jquery');

$config['asset'][] = array('file'=>'slideshow.swf', 'needs'=>'swfobject');


File: /web/CodeIgniter_1.7.2/system/application/views/public/flash_intro.php

[removed][removed]
    <div id="flashcontent">
        <strong>You need to upgrade your Flash Player.</strong>
    </div>
    [removed]
        var so = new SWFObject("&lt;?php echo base_url();?&gt;/assets/flash/slideshow.swf", "sotester", "100%", "100%", "8", "#000000");
        so.addParam("allowFullScreen", "TRUE");
        so.addParam("scale", "noscale");
        so.addParam("menu", "false");
        so.write("flashcontent");
    [removed]



File: /web/CodeIgniter_1.7.2/system/application/views/public/container.php

&lt;?php
$this->load->view($this->config->item('backendpro_template_public') . 'header');
$this->load->view($this->config->item('backendpro_template_public') . 'flash_intro');
$this->load->view($this->config->item('backendpro_template_public') . 'content');
$this->load->view($this->config->item('backendpro_template_public') . 'footer');
?&gt;

created:

/web/CodeIgniter_1.7.2/assets/flash
'slideshow.swf'

/web/CodeIgniter_1.7.2/assets/flash/slideshow
contains the .xml and images-nn...XX.jpg

/web/CodeIgniter_1.7.2/assets/js
'swfobject.js'

Anyway you can check @

www.sexolina.tv/codeigniter_1.7.2

Probably there is an problem with loading .swf or?
Thanks

[eluser]adamp1[/eluser]
@shinokada: I'm afraid I haven't thought too much about how to allow the upgrade in every case. Can't you put it in an autoload?

Yes you should be able to take the application folder out of the system folder. You will also need to change the settings in config/matchbox.php to point to the new modules folder. It will now be ../modules rather than ../../modules.

@elektron: First of all since you have translated things into Croatian, then in the main application/config.php file you will have to change the line ($config['language'] = "english". That changes the default language to use.

You can't load a flash file as an asset. Assets can only be css + js