Jump to content


Popular Content

Showing content with the highest reputation since 01/16/2020 in Posts

  1. 4 points

    Featured Products BS

    Uploaded Update: Featured Products CE v2.1.0 Featured Products CE v2.1.0. (CE Phoenix) Compatibility: Phoenix 1.0.4.x Lower versions, please use Featured Products CE v2.0.0. You may use the store side files of this version Featured Products CE v2.1.0. for Phoenix 1.0.2.x-1.0.3.x stores. Changes version 2.1.0.: Updated for OSCOM CE Phoenix 1.0.4.x Updated index content module template files to match Phoenix 1.0.2.x-1.0.4.x product modules Removed word length settings Bootstrapped Admin/featured.php and Admin/select_featured.php Removed Catalan and French admin language files Translated Spanish and German admin/select_featured.php language files Added Spanish and German store language files Updated instructions
  2. 2 points

    Phoenix Dashboard

    Thank you very much @JcMagpie and @ecartz for your explanations. I'm going to play a little with github to see if I learn something new. Anyway, I consider that for a simple user to use github is not a friendly way to update OSC and I suggest that for next official versions a easily and Friendly guide to how to change from to (for example) be published as Dan suggests. regards Valqui
  3. 2 points

    Phoenix - Russian Language Pack

    Спасибо Fredi @Fredi за поддержку oscommerce !!!
  4. 2 points

    Upgrade Path TO Phoenix

    Dan is correct and glad you found the solution. To others - if this will help - take a look at that error message that Krisz1 got: I'm sure this is like explaining 2+2 to some of you, but when I saw similar messages, I keyed on the "Unknown column" part. That tells you there's a field (column) missing in the database table the follow-on SQL statement is trying to access. Then I looked in the SQL "Select" statement for the "from" word. The name that comes after the "from" word in the SQL statement is the database table. You will also see the "products_gtin" field name in the collection of field names that the "Select" statement is trying to gather. So in this case, "products p" looks like the source table for the SQL statement. I don't know enough about SQL to know if the comma after that is specifying another table. I also don't know what the "p" means at the end of "products," or at the beginning of the field (column) and table names, but that doesn't matter. I'm going to check the "products" table, first. With those partial bits of information, go to the phpAdmin (or whatever client you're using) and find the "products" table in the database. Look at the structure for the "products" table in 2.3.4 and then look at the structure for the "products" table in Phoenix. In phpAdmin, there's an actual tab for "Structure." That should show you the extra fields (columns) existing in 2.3.4 that you need to add to Phoenix. You should see the "products_gtin" field in the 2.3.4 "products" table (in this example). Develop a similar SQL "Alter" statement as above, adjusting/editing for the variable type (TEXT, VARCHAR(##), etc.). Run that in the SQL window in phpAdmin on the database (don't touch the 2.3.4 one), then re-load the Phoenix store page that caused the error. It should go away. Or, at least the error changes to something else that you can also research similarly. Eventually, you should arrive at no errors when you re-load the store's page in question. Interestingly, I don't have a "products_gtin" field in my "products" table - either 2.3.4 or Phoenix. That's probably because I never installed the same add-ons that you guys did. So, maybe everyone arguing against a do-all script is correct. I had a horrible experience in the past trying to use an all-at-once SQL script for porting an OsC database (coming from MS2.2 to 2.3.4). Granted, it's not a single button-push, but maybe it really is better to encourage the logic and method of manually copying the database. Remember to back up, back up, back up - both before and after. 😉 This is very rudimentary, but hope it helps ...
  5. 2 points

    Article Manager v1.0

    Unfortunately your not the first to do this and I doubt you will be the last. PreastaShop claimes about 250,000 shops curently and is popular ( I use it on a site). It too is very moduler but ships with most of the key modules ready to install if not installed. However they have had issues, I belive if you check it's wiki page they state, "In October 2019, PrestaShop closed the Miami headquarters and ceased its operations in the Americas.[10] The current and latest version of Prestashop is[11]"
  6. 2 points
    I will try using the postcode in the query but I think it may throw some weird results as I know I have some customers who are neighbours. I will let you know how I get on so thanks for the suggestion.
  7. 2 points
    Simply go to your admin and change the number of items to be display on each screen size.
  8. 1 point

    Support ticket for Phoenix

    Added Support ticket module in Marketplace Support ticket for Phoenix module. Compatibility: Phoenix Tested on OSCOM CE Phoenix PHP 7.3 All credit goes to the original developer: Copyright (c) 2003 Henri Schmidhuber IN-Solution and all other contributers of previous versions. Many thanks to Lee Foster for his great participation in the modernization of this module. Code corrections have been made to adapt to php 7.3, for Phoenix and for the standard module menu in the Admin. The addon includes 2 languages: English and Russian. Full Package. Simply copy over the files and install and turn on the new add-on. Go to Modules -> Dashboard -> Install Module -> Support Tickets -> Install Module Set options through Modules -> Dashboard -> Support Tickets
  9. 1 point

    KissIT Image Thumbnailer Support

    This is the new support thread for: KissIT Image Thumbnailer Phoenix and KissIT Image Thumbnailer CE
  10. 1 point

    help what version

    Some version of osC boostrap! what goto Admin -> Tools -> Version Checker But it will not tell you much as it could be any thing from gold to frozen....
  11. 1 point

    Article Manager v1.0

    You're better off taking @Jack_mcs advice and paying someone on here to do your install. A lot of the addons that are coming out are plug and play and those that aren't are being adapted so they can be. Spend your money on the supporters pack, and pay someone here to set it all up for you. Updates are no fuss because of the slim core, there are loads of free addons being converted daily to Phoenix standards and that's before you even mention the supporters codes. These are coming from both the main dev team and the other supporters.
  12. 1 point

    Upgrade Path TO Phoenix

    https://stackoverflow.com/a/193860 SELECT DISTINCT TABLE_NAME FROM INFORMATION_SCHEMA.COLUMNS WHERE COLUMN_NAME = 'customers_id' AND TABLE_SCHEMA='YourDatabase'; Replace YourDatabase with whatever DB_DATABASE says in includes/configure.php define('DB_DATABASE', 'osCommerce'); The default (as shown here) is osCommerce, but it may be different in your shop. And of course the customers_id is particular to this issue. In this particular case, the customers_info table is also necessary but does not show. Because it uses customers_info_id instead of customers_id. You don't need the temporary data from whos_online which uses customer_id instead of customers_id.
  13. 1 point
    Last video got deleted by mistake!
  14. 1 point
    Sorry @artfulweb I must have missed your post as I was busy traveling over the holidays overseas. Yes I know I turned it of on small screens as it's not much use as it either one slide or very small slides that are not readable. If you wish to turn it back on then you need to change the class used in the following file public_html/includes/modules/content/index/templates/tpl_cm_i_jcm_new_products_carousel.php around line 283 find <!-- carousel slide output --> <div id="i_new_products_carousel" class="col-sm-12 mb-2 d-none d-md-block"> and change to, <!-- carousel slide output --> <div id="i_new_products_carousel" class="col-12 mb-2"> Then it will show on small devices.
  15. 1 point

    Information Pages SEO addon

    Thanks for the suggestion. I will add a note about that.
  16. 1 point

    Support ticket for Phoenix

    The module has been updated.
  17. 1 point

    Article Manager v1.0

    Please explain what this means in more detail. Have you enabled the box in the settings and installed the module? This version was written before Phoenix was released so there will be things like that that don't apply. The next version will have a Phoenix-specific set of files.
  18. 1 point

    Improvement proposal for OSC.

    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 Excellent contribution! LIKE!
  19. 1 point

    Improvement proposal for OSC.

    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.
  20. 1 point

    Phoenix - Russian Language Pack

    CE-Phoenix-Russian-language. Upgrade to full version Thanks Yurius for testing and help. Send to apps.oscommerce.com/v=cephoenix10&c=languages
  21. 1 point

    Phoenix - Russian Language Pack

    Thanks for the next update for Phoenix! I propose to lay out a complete package for this version for those who first download this product. What about the translation for the "Configuration" section? Also, in the product card there are problems with the translation. Are you planning to fix this?
  22. 1 point
    @Mikepo, @Omar_one, @Heatherbell, @peterpil19, What I mean is too much work to take a new copy of Phoenix and add all my previous installed modules and modifications. In my case (and maybe for some of us), it is faster to adapt the new features of Phoenix (new files) to old sites responsive (2.3.4BS or CE). NB: It depends on the level of modification of the site of each member. At no time did I say that we should not migrate to Phoenix code... Sure Phoenix's code is the future and we are grateful to @burt for his immense work. Without him Oscommerce CMS would be of the past.
  23. 1 point

    Ancient Coin Traders - Phoenix

    Hi @peterpil19, very nice page !!! I personally love carousels since they are very useful on mobile devices. Very nice your page: elegant, simple and easy to use. Great job!! Best regards Valqui
  24. 1 point

    Sub Categories in CE Phoenix Styling

    in the bm_categories.php file change line 40 to $OSCOM_CategoryTree->setParentGroupString('<div class="list-group list-group-flush phoenix">', '</div>', false); then in user.css add .phoenix a { padding-left: 50px; } which gives you
  25. 1 point
    messageStack extends alertblock, make sure that's at the top of your class i.e. class messageStack extends alertBlock { Then make sure includes/classes/alertbox.php is being included in application_top.php i.e. require('includes/classes/alertbox.php'); require('includes/classes/message_stack.php'); $messageStack = new messageStack;