Jump to content

Pronux

Members
  • Content count

    98
  • Joined

  • Last visited

Everything posted by Pronux

  1. I never experienced these two problems but I will check it on my demo site. Thanks for your feedback.
  2. @izzystradlin: take the code from farbor: http://forums.oscommerce.com/topic/368874-tab-menu-section-tms-and-pronux-tms-for-admin-support-thread/page__view__findpost__p__1556698
  3. At the demo site it seems to work: http://oscommerce.pronux.ch/product_info.php?products_id=28 Try to make some changes to the TMS Conf.php -> f.e. reduce the no of tabs, change the width of tab 2 etc. Or install the demo app from the zip package and test if it works on your domain.
  4. Sounds weird. I'm also using a clean install of osc 2.3.1 and the uploaded TMS-files should be the same as on my demosite. Can you provide me a link to your site?
  5. Programming quote of the day: “The Internet? Is that thing still around?” (Homer Simpson)

  6. I know only the "UltraPics - MS2 Image Addon Pack!" http://addons.oscommerce.com/info/1642 which looks different. If I were you, I would copy-past the code from 2.3.1 to your 2.2, is not that hard :thumbsup:
  7. farbor asked: Answer: It's not a contribution, it's the new picture module of osCommerce 2.3.1
  8. Quote of the day: “Never trust a computer you can’t throw out a window.” (Steve Wozniak)

  9. Of course, any software release can be either date-driven or quality-driven (it can't be both), but shipping is also a feature. Would be great :thumbsup:
  10. Pronux

    OSCOM 3.0

    Harald and his team is working day and night on the final version of OSCOM 3.0 and it will be great.
  11. Pronux

    OSCOM 3.0

    According to Harald, the release of OSCOM 3.0 is imminent: http://bit.ly/ef45Nm
  12. Last commit on the official osCommerce 3.0 GitHub repository: 20. August 2010 http://bit.ly/ego3br

    1. DunWeb

      DunWeb

      Yes, that's just about the time they started working on 2.3.1 but Mark says he is getting getting his second wind now so hopefully some progress will be made soon.

    2. germ

      germ

      Laments on the percieved lack of progress on any given project have no affect on the rate at which change occurs. Just my observation.

  13. @andyn Two tips: 1. What happens when you add the code from http://forums.oscommerce.com... to products_info.php BEFORE $TMS->tab[1]['content'] = $product_info['products_description']; $TMS->tab[2]['content'] = $reviewTabContent; $TMS->tab[3]['content'] = $contentTab3; 2. In PHP you can put text (string) into a varaible: $thisIsAVarialbe = 'this is a text string'; Now put all the generated review HTML-strings (that means all the review-content which is on the bottom of your products_info.php at the moment) into the variable $reviewTabContent. Do this BEFORE: $TMS->tab[1]['content'] = $product_info['products_description']; $TMS->tab[2]['content'] = $reviewTabContent; $TMS->tab[3]['content'] = $contentTab3; If it doesn't help, maybe StreamMan can post his solution here in this thread.
  14. @andyn If you have added the styles from TabMenuSectionStyles.css to your osCommerce stylesheet.css, you can simply ignore line 33 in TabMenuSection.php ($path = $this->CONF['pathtms'].'TabMenuSectionStyles.css'), it doesn't do anything. Reviews: I've provided an example in this thread how you can add the reviews to a tab. Insert the code on products_info.php before you add the content to the tabs: $TMS->tab[1]['content'] = 'content for tab 1...'; $TMS->tab[2]['content'] = $reviewTabContent; $TMS->tab[3]['content'] = 'content for tab 3...';
  15. You have to add the additional code on products_info.php. The inclusion and display of an entire file is not possible with TMS 1.0 Try the following code which I've taken from product_reviews.php after line 71. As I mentioned in my previous post, it does nothing else than putting the generated content into a temp variable ($reviewTabContent) and then adding it to tab 2. Important: I've not tested the following code, it's only an example how it could work...... $reviewTabContent = ''; $reviews_query_raw = "select r.reviews_id, left(rd.reviews_text, 100) as reviews_text, r.reviews_rating, r.date_added, r.customers_name from " . TABLE_REVIEWS . " r, " . TABLE_REVIEWS_DESCRIPTION . " rd where r.products_id = '" . (int)$product_info['products_id'] . "' and r.reviews_id = rd.reviews_id and rd.languages_id = '" . (int)$languages_id . "' and r.reviews_status = 1 order by r.reviews_id desc"; $reviews_split = new splitPageResults($reviews_query_raw, MAX_DISPLAY_NEW_REVIEWS); if ($reviews_split->number_of_rows > 0) { if ((PREV_NEXT_BAR_LOCATION == '1') || (PREV_NEXT_BAR_LOCATION == '3')) { $reviewTabContent = ' <div class="contentText"> <p style="float: right;">'. TEXT_RESULT_PAGE . ' ' . $reviews_split->display_links(MAX_DISPLAY_PAGE_LINKS, tep_get_all_get_params(array('page', 'info'))) .'</p> <p>'. $reviews_split->display_count(TEXT_DISPLAY_NUMBER_OF_REVIEWS) .'</p> </div> <br />'; } $reviews_query = tep_db_query($reviews_split->sql_query); while ($reviews = tep_db_fetch_array($reviews_query)) { $reviewTabContent .= ' <div> <span style="float: right;">'.sprintf(TEXT_REVIEW_DATE_ADDED, tep_date_long($reviews['date_added'])) .'</span> <h2><a href="' . tep_href_link(FILENAME_PRODUCT_REVIEWS_INFO, 'products_id=' . $product_info['products_id'] . '&reviews_id=' . $reviews['reviews_id']) . '">' . sprintf(TEXT_REVIEW_BY, tep_output_string_protected($reviews['customers_name'])) . '</a> </h2> </div> <div class="contentText"> '. tep_break_string(tep_output_string_protected($reviews['reviews_text']), 60, '-<br />') . ((strlen($reviews['reviews_text']) >= 100) ? '..' : '') . '<br /><br /><i>' . sprintf(TEXT_REVIEW_RATING, tep_image(DIR_WS_IMAGES . 'stars_' . $reviews['reviews_rating'] . '.gif', sprintf(TEXT_OF_5_STARS, $reviews['reviews_rating'])), sprintf(TEXT_OF_5_STARS, $reviews['reviews_rating'])) . '</i> </div>'; } } else { $reviewTabContent = ' <div class="contentText"> <?php echo TEXT_NO_REVIEWS; ?> </div>'; } $TMS->tab[2]['content'] = $reviewTabContent;
  16. @blr044: Jep, that's because of htmlentities.... I think that your text has the same color as the background of the tab content section and because of that you can't see it. Please try to change the background color and the color of the text and see if it works. And: Can you look into the HTML source code of this page in your browser ("View Page Source") and search for the content of $product_info['products_description3'], it must be there somewhere. Hope it helps.
  17. Should not be too hard: 1. You have to generate the reviews for the specific product (and store it into a temp variable), see how osc makes it on catalog/products_reviews.php after line 71 (osCommerce 2.3.1) 2. Load the content into a tab, for example: $TMS->tab[2]['content'] = $reviewTabContent; 3. Go to catalog/includes/TMS/Conf.php and change the name of the second tab: $CONF['tabs']['en'][2] = 'Reviews';
  18. @blr044: Please insert the following code and see if it shows the text: <?php //PRONUX TMS START include DIR_WS_INCLUDES.'TMS/Conf.php'; $TMS->tab[1]['content'] = $product_info['products_description']; $TMS->tab[2]['content'] = $product_info['products_description2']; $TMS->tab[3]['content'] = 'This is the third tab and this is the content START-|'.$product_info['products_description3'].'|-END'; $TMS->setLanguage('', $_SESSION['language']); $TMS->generateTabMenuSection(true); //PRONUX TMS END ?> And please try also: $TMS->tab[3]['content'] = htmlentities($product_info['products_description3']);
  19. Programming quote of the day: "Debuggers don't remove bugs. They only show them in slow motion." :-)

  20. @blr044: You have to locate the problem, f.e. does the third tab show text when you do this: $TMS->tab[3]['content'] = 'hello world 2'; If yes, echo the new db-field: echo $product_info['products_description3']; does it show the data? etc... @andyn: I'm sorry but there is no option to insert the text for the new fields (tabs) in the admin, which means you have to insert the content for the tabs manually via database at the moment. The reason for this missing feature is simple: We made this add-on for our customers which has a lot of article data already in the database but no place to show it on the product_info.php page. Their article data come from an ERP system (we are specialized in end-to-end integration between osCommerce and Microsoft Dynamics NAV ERP System -> About Pronux), so they had no need for such an admin input feature. But we will release a new version of TMS in late January which will have an admin part for inserting content to specified tabs. If you can't wait, you can do it by your own, should not be tot hard: Just clone and alter the products_decription fields/code on catalog/admin/categories.php @foxp2: Thanks for the tip. For testing purpose the php error handling in our demo shop is currently set to: error_reporting(E_ALL); ini_set("display_errors", 1); I think this may cause the described problems. @ringo667 Upload the demo folder included in TMS to your root directory of the shop (f.e. www.yourshow.com/demo) and look if it works. ->If it doesn't work: I think you have a problem with your PHP configuration or an old version of PHP... ->If it works: Reinstall the TMS add-on in your shop. If it doesn't work, go through the 5 steps mentioned at the beginning of this thread
  21. Even on Christmas, the guys @nopCommerce are working day and night http://bit.ly/hgWod4

  22. It's quite simple: 1. Add the new field to your database, to the table products_description, for example name the new field "new_field". 2. Add the new field to the sql-query on product_info.php, near line 37, for example change $product_info_query = tep_db_query("select p.products_id, pd.products_name,......... TO: $product_info_query = tep_db_query("select p.products_id, pd.new_field, pd.products_name,...... 3. Add the new field f.e. to the second tab: $TMS->tab[2]['content'] = = $product_info['new_field']; merry christmas! :thumbsup:
  23. It's quite simple: 1. Add the new field to your database, to the table products_description, for example name the new field "new_field". 2. Add the new field to the sql-query on product_info.php, near line 37, for example change $product_info_query = tep_db_query("select p.products_id, pd.products_name,......... TO: $product_info_query = tep_db_query("select p.products_id, pd.new_field, pd.products_name,...... 3. Add the new field f.e. to the second tab: $TMS->tab[2]['content'] = = $product_info['new_field']; Mary Christmas! :thumbsup:
  24. categories.php and the code in install.txt are based on osCommerce 2.3.1, perhaps this was the reason for your first problem. The Notice-Errors: You have to change the PHP error handler in your installation: Go to catalog/admin/includes/TMS/Conf.php and outcomment the last to lines: //Error Handling (for debugging) //error_reporting(E_ALL); //ini_set("display_errors", 1); Design-Changes: Go to catalog/admin/includes/TMS/Conf.php and change the default (min-height) to a smaller value: $CONF['defaultContentSectionHeight'] = 10;
×