Improvement proposal for OSC.

[valquiria23 229]

New year, new hope, new horzontes. Happy new year to the oscommerce community!!!

I decided to create this new topic so that EVERYONE can contribute their visions and say what they would like to see in the new OSC oscommerce.

Here I put a first need that we users who are not English speaking found.

For many years the OSC admin was not updated.
Today some notable members of our community such as @raiwa and @ecartz are helping the core team update oscommerce and in this the Admin.

Today the language packs do not include the total translation of the admin. It would be good to consider for future versions to be able to fully translate also the admin, because there are users who do not speak English.

What does the community think about this issue? It is important that everyone says their thoughts.

Greetings and happy 2020.

Valqui

[♥14steve14 588]

I think language packs for shop and admin side should be addons and not part of core. There are too many languages to include otherwise. Some have already translated languages and uploaded them to the addons area so if they have not done all the admin then they eoither need to be told, or someone needs to update the package.

I also think that language packs should include things like different address and date formats which are easily changed.

[hungryfrank 62]

using international calender to be totally international.   Hebrew Chinese arabic Persian there are many .

considering that with the Aage of mobile there are less people interested in having a website  in the west.

Edited January 7 by hungryfrank

[hungryfrank 62]

and options and attributes are really a weak point something like option type and Qtpro should be integrated with a better option management page

[valquiria23 229]

3 hours ago, 14steve14 said:

I think language packs for shop and admin side should be addons and not part of core.

I totally agree.
The problem that in ADMIN part you can't have everything in multi language. There are things that are hard coded and core changes need to be made so you can also have them in multi language. It is what I suggest to be added in the next versions. It would be nice for the core team to take these suggestions.

BR

Valqui

3 hours ago, 14steve14 said:

I also think that language packs should include things like different address and date formats which are easily changed.

Excellent contribution! LIKE!

[domiosc 22]

Convert all advanced modules into serial features.
There are many apps name how advanced: advanced customers, advanced orders, advanced specials,  advanced cart, advanced attributes, advanced product manager...

Default data managers are very simple, we can't even sort, search, add or remove columns, bulk actions, or edit from the list without going into detail.
These characteristics should be common in all areas together ajax.

Warehouses manager where can define and set options and stock sync by different protocols.

Extra fields especially in product data, model2, units by package, minimum and maximum stock, reorder level, multiplier units, delivery time, availability when out stock, by warehouses

Different levels of administration users, and configurable areas for they can view.

but of course all these should be modules about 1000's

and much more xD so add 1000's more

look this yes is a module voice search

 

That a feature should not be in the core can come in modules already integrated, but you have to make it easier for the public on foot to have these and many other features without complications.

Click. Click, all ready, and now use time to activate your need.

[Fredi 94]

This is an important issue. The language definitions for the Configuration table are hardly included in the installation code and in all modules that are added. This needs to be changed.
As a temporary solution, I added the Russian_Configuration1.sgl file to my Russian language package. If you upload this file to a new installed store using for example phpMyAdmin, all language constants in the database are changed to Russian. But each new addon makes entries in the Configuration table in English.
This can also be changed by editing the lines in each add-on and changing the language definitions, for example like this:

bm_whats_new.php

    function install() {
      tep_db_query("insert into configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) values ('Enable What\'s New Module', 'MODULE_BOXES_WHATS_NEW_STATUS', 'True', 'Do you want to add the module to your shop?', '6', '1', 'tep_cfg_select_option(array(\'True\', \'False\'), ', now())");
      tep_db_query("insert into configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) values ('Content Placement', 'MODULE_BOXES_WHATS_NEW_CONTENT_PLACEMENT', 'Left Column', 'Should the module be loaded in the left or right column?', '6', '1', 'tep_cfg_select_option(array(\'Left Column\', \'Right Column\'), ', now())");
      tep_db_query("insert into configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added) values ('Sort Order', 'MODULE_BOXES_WHATS_NEW_SORT_ORDER', '0', 'Sort order of display. Lowest is displayed first.', '6', '0', now())");
    }

Change to:
 

    function install() {
      tep_db_query("insert into configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) values ('Включить модуль Новинки', 'MODULE_BOXES_WHATS_NEW_STATUS', 'Да', Вы хотите добавить этот модуль в ваш магазин?', '6', '1', 'tep_cfg_select_option(array(\'True\', \'False\'), ', now())");
      tep_db_query("insert into configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) values ('Расположение модуля', 'MODULE_BOXES_WHATS_NEW_CONTENT_PLACEMENT', 'Левая колонка', 'Расположить модуль в левой или правой колонке?', '6', '1', 'tep_cfg_select_option(array(\'Левая колонка\', \'Правая колонка\'), ', now())");
      tep_db_query("insert into configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added) values ('Сортировка', 'MODULE_BOXES_WHATS_NEW_SORT_ORDER', '0', 'Сортировать для показа. С меньшим номером будет показан выше.', '6', '0', now())");
    }

Some Constants are repeated in almost all module boxes:

"True"
"Do you want to add the module to your shop?"
'tep_cfg_select_option(array(\'Left Column\', \'Right Column\'
'Sort Order'
'Sort order of display. Lowest is displayed first.'
 

We need 1 universal language file in the Admin to solve the problem and add several language constants to the language files of a particular module, if necessary ...

But for this you need to change the rules for writing modules. This needs to be coordinated with the coders and the community.
Such a replacement will simplify the writing of modules, facilitate the code and make the admin multilingual.

File Russian_Configuration1.sgl  Autor @Yurius

[hungryfrank 62]

I haven't tried this but u might want to take a look

https://apps.oscommerce.com/kKJ9a&multilanguage-support-for-configuration&p=2

Edited January 17 by hungryfrank