Jump to content
Latest News: (loading..)

Search the Community

Showing results for tags '2.4'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News and Announcements
    • News and Announcements
    • Partner Announcements
    • Ambassadors
  • Commercial Support
    • Developer Feedback
  • osCommerce Online Merchant v2.x
    • General Support
    • Installation and Configuration
    • Upgrading from Earlier Versions (v2.x to v2.x)
    • Add-Ons
    • Tips and Tricks
    • Security
  • Development
    • osCommerce Online Merchant v2.4
    • osCommerce Online Merchant Community Bootstrap Edition
    • osCommerce Online Merchant v3.x
    • Development Proposals
  • General
    • Next Steps / Optimizations / Marketing
    • Live Shop Reviews
    • E-Commerce Laws
    • General Discussions
    • PHP / SQL / Web Design
  • oscBooks and oscTemplates's Announcements
  • PayPal's Announcements
  • Sage Pay's Announcements
  • Solomono - new level osCommerce templates's Announcements
  • German Community's OSCOM v2.x
  • German Community's Allgemein
  • German Community's OSCOM v3.x

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Real Name





Found 3 results

  1. Hello, I will have a big problem with the actual code when you want to insert a modal boostrap with a call to external files. The modal displays the header and the footer inside. This tutorial help you to include a modal boostrap with an external element inside the modal without the header and the footer Thank you to @Harald Ponce de Leon for this help. I hope, it will be integrate inside the core. 1 step : include a new function in /OM/PagesAbstract.php just before public function useSiteTemplate() add public function setUseSiteTemplate($bool) { $this->use_site_template = ($bool === true); } 2nd step : Modal boostrap now we suppose you want to include a modal inside a file. For example in edit.php Add this element : the modal boostrap where you want. (Sites/Admin/Pages/Home/template/edit.php) <script> $( document ).ready(function() { $("#myModal").on("show.bs.modal", function(e) { var link = $(e.relatedTarget); $(this).find(".modal-body").load(link.attr("href")); }); }); </script> <?php //******************************** // call pop up inside Amin/Pages //********************************* ?> <a href="<?php echo $OSCOM_Manager->link('PopUp'); ?>" data-remote="false" data-toggle="modal" data-target="#myModal" class="btn btn-default">Launch Modal</a> <!-- Default bootstrap modal example --> <div class="modal fade" id="myModal" tabindex="-1" role="dialog" aria-labelledby="myModalLabel" aria-hidden="true"> <div class="modal-dialog"> <div class="modal-content"> <div class="modal-header"> <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button> <h4 class="modal-title" id="myModalLabel">Modal title</h4> </div> <div class="modal-body"> ... </div> <div class="modal-footer"> <button type="button" class="btn btn-default" data-dismiss="modal">Close</button> <button type="button" class="btn btn-primary">Save changes</button> </div> </div> </div> </div> 3nd step : PoPup Actions In Sites/Admin/Pages/Home/Actions Create a class called PopUp.php namespace OSC\Apps\Communication\PageManager\Sites\Admin\Pages\Home\Actions; use OSC\OM\Registry; use OSC\OM\HTML; class PopUp extends \OSC\OM\PagesActionsAbstract { public function execute() { $this->page->setUseSiteTemplate(false); // ad this function inside the files $this->page->setFile('popup.php'); } } 4 step : Popup template In Sites/Admin/Pages/Home/templates Create a class called pop_up.php <?php use OSC\OM\HTML; ?> <div class="row"> <div class="col-sm-12"> <div class="panel panel-primary"> <div class="panel-heading">Heading</div> <div class="panel-body"> Put Your stuff in here <?php echo HTML::inputField('example', 'toto'); ?> </div> </div> </div> </div> That's all ! After you can continue your code with save, insert, update ...
  2. Plaiyng as usual with osc code, i'm wondering if can be a good idea to have a multilingual install to make more easy the installation process. I'm thinking to implement this as the language to translate is not too much, for the most common languages(deutsch, french, espanol, italian, portuguese ) Do you think it can be usefulll?
  3. panicgripdesigns

    osCommerce 2.4 Roadmap

    I've noticed that the long topic about the status and development of osCommerce 2.4 seems to have vanished, which is very disappointing. Is osCommerce 2.4 still planned as the next major release? If so, I would very much like to help build a roadmap with a list of the major overall goals of the release. Times could of course be left off, but any forkers our there would have clear cut idea of the goals and what the community wishes to accomplish with 2.4. So far, from the changes to the codebase and the work done in the 24 branch on the various forks, it seems these are the plans: Catalog - $OSCOM_Template - Reorganize code and overhaul Catalog to use new modular $OSCOM_Template system. - Mostly Complete Catalog - Bootstrap - Use Twitter's Bootstrap layout/css3/html5 gridlayout & design resources to modernize look of Catalog. - Mostly Complete with v. 2.3.0 (Depricated) Admin - $OSCOM_Template - Reorganize code and overhaul Admin to use new modular $OSCOM_Template system. - ? Admin - Bootstrap - Use Twitter's Bootstrap layout/css3/html5 gridlayout & design resources to modernize look of Catalog. - ? Admin & Catalog - Bootstrap Upgrade - Upgrade to Bootstrap 3.x (Currently v3.0.3 [getbootstrap.com]) Admin & Catalog - Php Upgrade - Improve compatibility with php 5.5 (Current Stable PHP 5.5.7 [php.net]) The following are verbatim from a Feb 06, 2013 post by HPDL Backport v3.0 database class; use prepared statements; possibly InnoDB foreign keys and transactions by default (only support MySQLi); use cache Add more classes to clean up the codebase (eg, customers class) Fix checkout procedure so process code is not duplicated in payment modules Rename tep functions to osc and optimize each function in the process (to php53) Possibly move language definitions to ini files or to the database Please correct me if I'm wrong, and I will gladly update the above list. P.S. If this is redundant and there is already a roadmap / todo list, you can disregard the above, but please provide a link. I'm dying to try to help in some way.