burt

http://addons.oscommerce.com/info/8864
 
Now includes a fileset for bootstrap osCommerce

http://addons.oscommerce.com/info/8864
 
Now includes a fileset for bootstrap osCommerce

Even if you used and modified easy populate surely you have to write unique meta tags by typing them in ne t a time.

You can do it in phpmyadmin, but that defeats the purpose of creating especially crafted titles and descriptions, no?

Then you're only a year older that me. If I can still learn new things, and I do so as often as I can, then you can do it as well. Might as well start now.
 
Regards
Jim

you could just add a tep_session_registered into all files other than;
 
login.php
and
create_account.php
 
That should do it ? Look at how this is done in (for example) account.php.

"Big Chooser" from @@swguy would appear to fit the bill. Commercial product and fairly difficult to set up but should do what you want (I think).

Joe, I can guarantee this will never happen. What you want is not what the next shop would want is not want the shop down the road would want.
 
These two addons are not suitable for inclusion into core; individual shopowners would be expected to muddle through OR if they can't muddle through, they pay a developer for a customised version of osCommerce that does do exactly what they need it to do.
 
In general, and this advice is for all users of osc who require "something" added into the core, ask yourself;
 
is it good for 99% of shops or am I only thinking of my shop
 

$name_query = tep_db_query("select products_name from " . TABLE_PRODUCTS_DESCRIPTION . " where products_id = '" . (int)$HTTP_GET_VARS['products_id'] . "' and languages_id = '" . (int)$languages_id . "'");
 
 

Thanks @@burt,
Hello Raphael @@rafhun,
 
Small error in the query: should be "and language_id =" instead of "and languages_id =".
 
I also added the mobile session statement to ensure no mess in the classic page.
So the whole code snippet should be:

// add the products name to the breadcrumb trail for mobile if (MOBILE_SITE=='True' && isset($HTTP_GET_VARS['products_id'])) { $name_query = tep_db_query("select products_name from " . TABLE_PRODUCTS_DESCRIPTION . " where products_id = '" . (int)$HTTP_GET_VARS['products_id'] . "' and language_id = '" . (int)$languages_id . "'"); if (tep_db_num_rows($name_query)) { $name = tep_db_fetch_array($name_query); $breadcrumb->add($name['products_name'], tep_href_link(FILENAME_PRODUCT_INFO, 'cPath=' . $cPath . '&products_id=' . $HTTP_GET_VARS['products_id'])); } }
 
Please confirm and I will add this in the next update.
 
regards
Rainer

when i did winmerge....my version must have had it so i moved it over to the new one

I like the one that @@mattjt83 has coded. It is not free, but that is a good thing as it means you get a good product with good support.

This thread is a discussion area for a header tag module that will dynamically control a shops layout by page type.
 
The module divides the shops various pages into 6 types:
Home Page
 
Product Listing Pages
 
Product Info Pages
 
User/Account Pages
 
Static Pages
 
Checkout pages

The administrator has the ability to assign a layout to each of these page types, including a default fallback. Each page type can have an individual layout or they may all have the same layout.
 
No one would really want to change the layout from page to page that much, but there are certain situations where mixing layouts could work out well. For instance, one may want the checkout pages to be full page with no side columns in order to avoid distracting a customer during the order process.
 
Another instance could be that you want to limit distractions during account sign up. And yet another, maybe a shop would do well to have the home page formatted differently than the rest of the site so as to have room to really work that canvas into something appealing.
 
As Ive read here recently, sometimes the product listing areas just need to show a lot of information across the board. So while viewing a page full of products, one may see a lot of information, but once they click to view the actual product info page, then they may be greeted by a much simpler page that presents the product fully with no ongoing clutter or other distractions.
 
There are 7 different layout styles available:
2 Column 1 Sidebar Left
 
2 Column 1 Sidebar Right
 
3 Column Sidebars Both
 
3 Column 2 Sidebars Left
 
3 Column 2 Sidebars Right
 
1 Column Sidebars Bottom
 
Full Page (No Sidebars)

So how does it work?
 
The header tag module assigns a class to the body tag in order to use the relevant css style to load the desired layout. There are changes to template top and template bottom in order to get things going. An additional div is placed and the grid_* are removed from the left and right columns.
 
With these changes the complete structure becomes very flexible. There is one dilemma, and that is the 960gs. It is not bad to have the 960 grid in place, it makes a perfectly fine wrapper, but really, thats about it. Of course thats not a big deal, as there are only a few spots that really call upon it, and 2 have already been removed.
 
I do not want to write a contribution that tells people to remove the 960 grid in order to use it, so I will not touch much further on that, but will leave this in mind:
If removed, and the #bodyWrapper div is assigned a max-width of XXXpx and width of 100% - then the complete framework becomes responsive.
 
Since this module is basically a tool to aid in layout and design, it also goes a step further to lend towards the designer. Maybe theres a hot new product and it just needs to pop out from the other listings - maybe a store has need for landing pages that have their own overall look and feel. It would be nice to do these things and still hook into the primary functions of the cart software, without practically building a whole new set of pages and assets chained thereof.
 
So -- the answer, and I have tested this here and there through the years, add a unique css ID to the body tag as well. Now every thing on a page can be manipulated through the stylesheet alone. Design wise that is! Move things out of the way, hide things, recolor things, take something from the description, move it elsewhere - -
 
The module pulls the category name, manufacturer name, product name, HEADING_TITLE || NAVBAR || NAVBAR_2, and outputs that as a css friendly id. It may not sound like much, but it goes a long way. Its not something useful to all, but those that could make use of it would find it indispensable.
 
Installation is very simple:
Upload 2 files into header tags directory
 
Upload 1 file to header tags language directory
 
Upload 1 new stylesheet
 
Make slight changes to template_top
 
Make slight changes to template_bottom

Here are some examples using a standard osCommerce 2.3.4 setup. Besides the Dynamic Frame Controller installation, the only other change has been to remove the store logo to allow room to print the CSS ID and Class to screen.
HomePage => 2 Column 1 Sidebar Left => http://mulium.wsfive.com/
Product Info Pages => 2 Column 1 Sidebar Right => http://mulium.wsfive.com/product_info.php?cPath=3_10&products_id=11
Product Listing Pages => 3 Column Sidebars Both => http://mulium.wsfive.com/index.php?cPath=3_10
User/Account Pages => 3 Column 2 Sidebars Left => http://mulium.wsfive.com/login.php
Static Pages => 3 Column 2 Sidebars Right => http://mulium.wsfive.com/conditions.php
Checkout pages => Full Page (No Sidebars) => http://mulium.wsfive.com/shopping_cart.php
1 Column Sidebars Bottom <!-- no more pages groups available to show this one, but it is probably the least to ever be used. -->

If you resize your browser while looking at the examples, you'll find that it wants to take on a responsive form, but the grid has it trapped.
 
 
I dont have an install file written yet, but will be getting that together and would like to know if anyone would like to beta test.
 
All input on this idea would be greatly appreciated. It can be expanded even further, but I wish to make the most with less, and not create something that just goes too far.

It does not matter how technically proficient you are, you can help to speed up development of v2.4 osCommerce.
 
HERE IS HOW:
 
1. Download and install v2.3.3 => http://www.oscommerce.com/solutions/downloads
 
2. Play with it as much as you can. If you come across something that you think is a bug or inconsistency, post to the bug tracker => http://www.oscommerce.com/forums/tracker/project-1-oscommerce-online-merchant-v2x/
 
Someone will respond to your bug to let you know if it is a bug, and provide a fix.
Fixes for confirmed bugs will be rolled into 2.4
 
Let's get this community rolling! Do YOUR part to help bring osCommerce back the success it deserves.

And, if you can't help with the codebase, you can certainly help by purchasing a subscription.
 
Subscribers get some quite nice benefits, with some more benefits being planned.

I suspect your database entries are corrupted.
 
Uninstall ALL of your shipping modules, then use phpmyadmin to make sure that every shipping module is fully uninstalled.
Do the same for the Order Total modules.
 
Then re-install the shipping modules, and configure them.
Then re-install the order_total modules and configure them.
 
After doing this, report back.

Lack of feedback is in general because others don't understand your problem - if you don't take the time to explain things in detail, how do you expect others to spend their (precious) free time to help you ?
Personnally, I will help if I can, but if I can tell it is going to be a longwinded thread to get anywhere I give up before I start ... sorry - but that is just the way I approach this free forum

Really no point in any of those addons, all are outdated and just add more overhead. The most recent versions of osc already have code in place to deal with spammers and mail abuse.
 
Adding custom content to the page can easily be done through the language file or even with the banner manager.
 
If your going to build a fork, think it through very thouroughly. There are already a handful of loaded osCommerce builds available, everyone and his brother, mother, sister and talented dog has been there, done that. Theres a reason the core osCommerce is not "Loaded".
 
Good Luck

I'm thinking way too far forward, maybe because this system already exists...and is in use, with smartphone barcode scanning in fact.
 
The point is that should this shopowner want it, she could have a system that reads a bunch of orders, totalises the products to pick & puts the products into the correct pick schedule. In other words a picking system geared up to multiple orders with multiple products based on a route around the warehouse...just like how GSI do it.

This is not a good idea. Who is to say that 1 addon is better than another. If you are attempting to make a "loaded" version of osCommerce, then fork osCommerce on github and make the changes on there.
 
Something in the future will be a rating system for addons.

This is not a good idea. Who is to say that 1 addon is better than another. If you are attempting to make a "loaded" version of osCommerce, then fork osCommerce on github and make the changes on there.
 
Something in the future will be a rating system for addons.

This is not a good idea. Who is to say that 1 addon is better than another. If you are attempting to make a "loaded" version of osCommerce, then fork osCommerce on github and make the changes on there.
 
Something in the future will be a rating system for addons.

@@14steve14 - you are far more eloquent than me.
 
@@perbuch "Therefore I expect you will change your attitude from now."
No, YOU will change your attitude when you have a few more posts and realise how much crap gets posted in this forum, and usually crap forced on us by 3rd party "developers" who know next to nothing about osCommerce and expect their clients to get help here.

@@14steve14 - you are far more eloquent than me.
 
@@perbuch "Therefore I expect you will change your attitude from now."
No, YOU will change your attitude when you have a few more posts and realise how much crap gets posted in this forum, and usually crap forced on us by 3rd party "developers" who know next to nothing about osCommerce and expect their clients to get help here.

I agree. If someone uses a free, or even a paid for template, then support should be given by the template supplier. People on this forum should not be used by a template supplier for free support. We do not know the code and do not know what the supplier has done to the code. If support is not given with the templare then tough.