Jump to content
Latest News: (loading..)

Recommended Posts



Ah! I see... I don't know about the classes and functions never tried before.

I don't think that it would be all too difficult to achieve something like that. Need to compare both sides files and see what is different and merge them.

Then you have to change the paths for the classes and functions folders either inside the configure.php or in each single php file.

What kind of benefit that will give you performance wise I don't know.

Share this post

Link to post
Share on other sites

@@Tsimi, I am less of a concern with performance, but more to do with managing duplicate functions/classes. RAM's cheap...


I can see benefit in the current arrangement of keeping admin functions inaccessible to unauthorised access, so you could still have two places that things might be defined. So only one place to change, but maybe two places to look; a naming convention would help avoid wasted investigation time.


I've certainly wanted access to catalog functions on the admin side for customisations before; typically price/tax stuff.


There are some things with the same name and different definitions on either side.


Needs a bit of thought - and quite a lot of implementation effort!

For a new install or if your store isn't mobile-friendly, get the community-supported responsive osCommerce ( CE) here: https://github.com/gburton/Responsive-osCommerce/archive/2341-Frozen.zip

Working on generalising bespoke solutions for Quickbooks integration, Easify integration and pay4later (DEKO) integration at 2.3.x

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now