Jump to content
Latest News: (loading..)

Recommended Posts

Hello,

 

This may have been discussed already or not, just an idea:

 

The directories introduced in 2.3 series began to use prefixes to identify files, like ht_ for header tags, ar_ for action recorder and all the content modules have their identifier prefixes.

Wouldn't the 2.4 update be an opportunity to add these kind of prefixes to all files inside the includes and subfolders.

cl_ for classes, fn_ for functions, md_ for modules, lng_ for language files etc.

 

Advantages:

- easy identify files in wrong directories

- prevent different files with the same name be accidentally overwritten.

- easier identification of open files in editor tabs

....

or would this be a too big break with existing versions??

 

rgds

Rainer

Share this post


Link to post
Share on other sites

Hello,

 

This may have been discussed already or not, just an idea:

 

The directories introduced in 2.3 series began to use prefixes to identify files, like ht_ for header tags, ar_ for action recorder and all the content modules have their identifier prefixes.

Wouldn't the 2.4 update be an opportunity to add these kind of prefixes to all files inside the includes and subfolders.

cl_ for classes, fn_ for functions, md_ for modules, lng_ for language files etc.

 

Advantages:

- easy identify files in wrong directories

- prevent different files with the same name be accidentally overwritten.

- easier identification of open files in editor tabs

....

or would this be a too big break with existing versions??

 

rgds

Rainer

 

@@raiwa Great idea worth exploring for the reasons you mentioned.


Let's make things easier for new osCommerce users http://forums.oscommerce.com/topic/402638-discussion-about-hard-coded-database-tables/?p=1718900  Getting there with osCommerce 2.4! :thumbsup:

Share this post


Link to post
Share on other sites

@spidometrs 5.5 minimum


Regards
-----------------------------------------
Loïc

Contact me by skype for business
Contact me @gyakutsuki for an answer on the forum

Tuto for 2.4 :
- How to Display a new page with app
- How to make Header Tags under app APP
- How to make a
boostrap modal with external element

Share this post


Link to post
Share on other sites

The directories introduced in 2.3 series began to use prefixes to identify files, like ht_ for header tags, ar_ for action recorder and all the content modules have their identifier prefixes.

Wouldn't the 2.4 update be an opportunity to add these kind of prefixes to all files inside the includes and subfolders.

cl_ for classes, fn_ for functions, md_ for modules, lng_ for language files etc.

All legacy classes will ultimately move to a namespace level in the OSC\OM framework and all external modules will ultimately reside in a self-contained App.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

OSC 2.4. It will support multiple stores from one admin?

Edited by spidometrs

No outside url's in signatures allowed - thanks

Share this post


Link to post
Share on other sites

Hi All..

 

As stated earlier, the minimum PHP version for v2.4 going forward is v5.5. The minimum MySQL version is now v5.1.38 as the tables will slowly be converted to InnoDB to take advantage of transactions and foreign keys.

 

New v2.4.0beta1 installations will already be setup for InnoDB. The next beta releases will introduce transactions and foreign keys.

 

When the v2.3 upgrade routine becomes available, a database table check-up function will be available in the Administration Dashboard that compares the upgraded database tables to the core database tables. A hint of how this will be possible can be seen in v2.4.0beta1 with the database schema moving from raw sql to a simple text file layout:

 

https://github.com/osCommerce/oscommerce2/tree/master/catalog/includes/OSC/Schema

 

MySQL/MariaDB/etc versions up to the latest 5.7 works fine - the strict sql mode is also being forced to make sure no sql errors occur in the core or in Apps.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

I still do not understand why one brand store - has two versions of the code.
It disperses forces community..
But you know better ...

Edited by spidometrs

No outside url's in signatures allowed - thanks

Share this post


Link to post
Share on other sites

I still do not understand why one brand store - has two versions of the code.

It disperses forces community..

But you know better ...

Thank you for your trust :)

 

v2.3/v2.4 is built on a codebase that is over 16 years old which was not developed with multiple-stores in mind. Developing this will introduce a lot of code changes for a feature a minority of our users will use.

 

Modernising the codebase in the development of v3.0 makes it easier to add multiple-stores, however again this is not currently something we are interested in working on. Maybe for v4.x in the future as a core feature, but not now.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

Thanks for the quick response.
I'm glad you all came back to the development of the new version.
This is for me a positive event.
I really hope that you will have the mood for version 4.

Thank you, but that you are here.

Edited by spidometrs

No outside url's in signatures allowed - thanks

Share this post


Link to post
Share on other sites

hello

 

can not wait to see the beta version for download

 

just one question :

 

where can i read about apps / hooks and how they change the way to extend the core code in comparison with the current modules for content, payment etc.

 

thanks

eric

Share this post


Link to post
Share on other sites

And just another question : Will the standard module structure stay on 2.4 or will these modules (like boxes, shipping, navar, header tags...) be removed?

Edited by piernas

Share this post


Link to post
Share on other sites

where can i read about apps / hooks and how they change the way to extend the core code in comparison with the current modules for content, payment etc.

 

Documentation will be available soon.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

And just another question : Will the standard module structure stay on 2.4 or will these modules (like boxes, shipping, navar, header tags...) be removed?

 

The core modules will more than likely stay in their current module directories. Add-Ons should be developed as Apps and have their modules defined in the App's oscommerce.json file. This will be extended on in the next beta release as it's currently only taking the following into consideration:

 

Administration Dashboard

Administration Menu

Payment

Content

Hooks


:heart:, osCommerce

Share this post


Link to post
Share on other sites

According to Harald (http://forums.oscommerce.com/topic/410369-install-on-new-lamp-server-php7-and-mysql-5/?p=1749255) it looks like he's planning an intermediate 2.3.5 release. I hope this is more or less 2.3.4BS Edge (or an updated Gold), so we can get away from having an unofficial community version that most of the world doesn't know about (many kudos to Gary). This would be excellent, as it permits unhurried and careful development of 2.4 (many kudos to Harald), rather than feeling pressured to get it out the door as soon as possible.

 

Can we assume this (2.3.5) is an official statement? Hopefully it's not a typo or Freudian slip!

Share this post


Link to post
Share on other sites

v2.3.5 is a bugfix release from v2.3.4.

 

v2.4.0beta is what v2.3.x and BS users can and should upgrade to when the production ready release is ready. There will be weekly beta releases leading up to the production ready release.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

We can hope to obtain a template system in 2.4?

Please.

 

There's a system to be able to load different templates however the page content still contains PHP code. This can be worked on for a future v2.x release series.

 

v3.0 already has a full PHP-less template implementation however that release is still in development.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

There's a system to be able to load different templates however the page content still contains PHP code. This can be worked on for a future v2.x release series.

 

At least so.

We need to try to make a completely separate from PHP.

Then designers can create templates.


No outside url's in signatures allowed - thanks

Share this post


Link to post
Share on other sites

Hi All..

 

v2.4.0beta will start using the password_hash() functions from PHP 5.5 to hash user account passwords. This is handled by the OSC\OM\Hash class and takes legacy phpass and salt passwords into consideration. Legacy passwords are automatically rehashed and stored in the database when the user logs in, similarly as to how phpass upgraded salt passwords.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

v2.4 will have a built-in import/export products?

 

Do mean like a built-in Easy Populate? That would certainly be a nice feature, so long as there's an API to add additional formats (XML, etc.).

 

What kind of uses would you have for a product export? I'm wondering if it would be useful (commonly used) enough to warrant a place in the base product. Do people export product entries to other sales systems (eBay, Amazon, brick and mortar POS, etc.)? Would they be better off creating a common file offline, and importing it to osC and these other systems?

Share this post


Link to post
Share on other sites

v2.4 will have a built-in import/export products?

At least one format? CSV or XML?

 

Not at the start as a core feature. This can be looked into for v2.5 or so. This would make a very nice App though if someone is interested in taking care of it.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

If v2.4 has import/export products, then the user can easily move from a different store or brand.
It is also easy to start selling, if you import products from the the wholesale supplier.
This is one of the main criteria by which the user selects the store script.
Now no one wants to make 100 hand products. And 300 products? ..

But decide for yourself.


No outside url's in signatures allowed - thanks

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

×