Jump to content

Archived

This topic is now archived and is closed to further replies.

scandic_outlet

OsCommerce v 2.3 - when?

Recommended Posts

We have put a lot of effort into fixing all reported security issues with the 2.3 release which should make the need to install any mods to secure your site unnecessary.

I would presume that this does not include the renaming of "admin" to something of your choice, but hopefully clear instructions will be provided. I know that file_manager and define_language have been removed; I don't know what other steps have been taken.

 

Note that a properly coded xhtml based layout does not mean no tables.

I doubt that the 2.x series will ever see a full CSS-driven tableless layout; it's just too massive a change, at least for the upcoming 2.3. There is an add-on or two to do this, but I can understand any reluctance to incorporate this into the 2.x base code, as it would break many existing add-ons. I would hope that 3.0 will be mostly tableless...

Share this post


Link to post
Share on other sites

I would presume that this does not include the renaming of "admin" to something of your choice, but hopefully clear instructions will be provided. I know that file_manager and define_language have been removed; I don't know what other steps have been taken.

 

As long as the permissions are set its possible to rename the admin folder during installation thumbsup.gif

 

A number of other things have been done to secure the application and numerous tools used to find any unsuspecting issues which haven't been reported yet, suffice to say 2.3 has been through some very rigorous testing in terms of security issues.


Mark Evans

osCommerce Monkey & Lead Guitarist for "Sparky + the Monkeys" (Album on sale in all good record shops)

 

---------------------------------------

Software is like sex: It's better when it's free. (Linus Torvalds)

Share this post


Link to post
Share on other sites

I would presume that this does not include the renaming of "admin" to something of your choice, but hopefully clear instructions will be provided.

 

Renaming the admin folder is a part of the pre-installation process.

See the "Online Store Settings" image at www.clubosc.com/oscommerce-rc3-installation-is-super-simple.html

Couldn't be clearer or easier.


Help shape the future of Phoenix; join the Phoenix Club

Share this post


Link to post
Share on other sites

There is no change in the underlying code that produces the layout, other than to move common components into template_top.php and template_bottom.php

 

Once 2.3 is released, I will be implementing a properly coded xhtml based layout as and when time permits.

 

Note that a properly coded xhtml based layout does not mean no tables.

 

I've used the osC to CSS add on and it's fantastic. I was hoping that the next version would have had CSS to a similar level. Means I'll have a whole load of work to do going through each page and making the admendments, unless someone makes an add on for the new osC verion :D Thanks everyone for the info on the forthcoming release :)

Share this post


Link to post
Share on other sites

When will the v2.3 be public?

I want to create a new osC shop, but it is not very wise to use an older RC when the new version is probably uploaded very soon

Share this post


Link to post
Share on other sites

http://www.freelancephp.co.uk/2010/09/18/love-thy-project/

 

A majority of people in the community are pretty understanding about the dedication you bring to a project and understand when you don't provide firm commitments on when something will be ready (a.k.a "it will be ready when its ready")

 

Why stress over it? It's ready right now @ Github if you are able to do more than just download it and expect it to be 100%. Help to make this better rather than keep asking "are we there yet".


Help shape the future of Phoenix; join the Phoenix Club

Share this post


Link to post
Share on other sites

To be honest with you, not only do I not feel comfortable just downloading it and hoping I don't miss anything important that gets done to it after I do, (I really do need for it to be 100% of whatever it's going to be) I'm not even sure where on @Github you click for the download. I see the current and older versions, but nothing that looks like 2.3


Oscommerce site:

 

 

OSC to CSS, http://addons.oscommerce.com/info/7263 -Mail Manager, http://addons.oscommerce.com/info/8120

Share this post


Link to post
Share on other sites

It's the [download source] button.

 

It is people who are unwilling to help that are causing the timeline to extend.


Help shape the future of Phoenix; join the Phoenix Club

Share this post


Link to post
Share on other sites

It's the [download source] button.

 

 

I see it, thanks.

 

'It is people who are unwilling to help that are causing the timeline to extend'

I can understand not helping = not speeding things along, but = slowing it down? In all kindness, do you need another cup of coffee or a longer nap?

 

I'm willing to add my feeble skills, but I wasn't asked to help.

 

I looked at the new template_top.php. Here is my 2 cents, hopefully this come off as advice, not so much as criticism.

 

template_top.php has the entire header in it. BOTH the opening and closing header tags. The catalog pages have no header info in them at all. This is worse

than the current situation.

 

For example, currently if you would like to add, say JQuery ui tabs, to product_info.php you add the javascript file reference to the header of product_info.php and then you add a little bit of scripting particular to that page just before </head> on product_info.php. With the system in 2.3, to add the javascript reference and scripting to the header, you have to do it to in template_top.php. In other words, if a shop visitor clicks on say, his account information in account.php, then that visitor, is going to wait for the javascript programming specific to the product page to load before it's possible to change the email address. Pointless.

 

Can you imagine how a shop is going to run with all the javascript programming used for 'pretty photo' or 'one page checkout' or others, having to load every single time there is ANY page change?

 

The fix is so simple it's ridiculous -> Take the closing </head> out of template_top.php place it on every single catalog page. That way, if you want a site-wide javascript reference, like the main jquery file, or a site-wide stylesheet reference, put it below the <head> tag in template_top. If you only want it on product_info.php, put the javascript or stylesheet reference just above the </head> tag on product_info.php.

 

Thats the way the OSC to CSS contribution does it, with it's includes/template_top.php file and it works fine.


Oscommerce site:

 

 

OSC to CSS, http://addons.oscommerce.com/info/7263 -Mail Manager, http://addons.oscommerce.com/info/8120

Share this post


Link to post
Share on other sites

"slowing it down" - is not quite what I said.

 

Without people downloading and using for testing, no feedback is being provided. No feedback means no immediate release. No release = timeline extending.

 

All it would take is 10 or 20 knowledgable people like yourself to provide the type of feedback you have in your previous post, which can be answered or looked at again with regards to changing it. If those people each caught 1 bug or came up with one idea, it would be a real boon to the community and to osCommerce, wouldn't you agree.

 

Anyway, the getheadertags functionality could be used to insert a js file on a given page (eg product_info for prettyphoto or fancybox or whatever is preferred).

 

Alternatively, it is simples to basename the script being accessed and load like that from template_top - pseudocode;

 

if (basename($_SERVER['SCRIPT_FILENAME']) == FILENAME_PRODUCT_INFO) include('whatever.js');

 

By the way, I wasn't asked to help either, but that doesn't stop me from making my views known and providing code and or ideas and or bugfixes for consideration. If some of my changes make it, great. If not, I can say I tried.


Help shape the future of Phoenix; join the Phoenix Club

Share this post


Link to post
Share on other sites

I see what you mean, no feedback hurts.

 

The 'getheadertgs' and template_top - pseudocode however is getting a bit beyond my paygrade. My concern is this, and perhaps the code you mention solves my concern, or not. I'll be specific in my scenario.

 

To install 'JQuery pretty photo' you place a two javascript file references in the header ( I know you know this, I'm just setting up my question) . I see that the main javascript 1.4.2 file is already included in template_top. Cool. Then you put a second reference to the javascript file specific to 'pretty photo'. Then you put in a bit of script specific to pretty photo just before the closing </head> tag. This second js reference and this second bit of code, should not be in the header of every shop page - only in the header of product_info.php (assuming that's where you are using it).

 

How could you accomplish this with both the opening and closing head tags in a common file like template_top? My thinking was that you put the opening head tag (and some header info) in each catalog page where you would normally see it. But where you would normally in each page expect to see the closing tag, there you reference template_top. And in template top you have the closing head tag. That way, if you want a page-specific js file reference or a bit of js code , you place it below the <head> in that page and above the reference, in that page, to template_top.

 

If you want a site-wide js reference or code you put it in template_top above the </head>. WIthout the <head> in a catalog page, I can't conceive of how you get around this issue, no matter how clever the pseudocode or getthingamybobtag. I understand that you can insert code with functions and whatnot, but how would you insert code on a specific page within it's head tags, when that page has no head tags? But I'm not a coder.


Oscommerce site:

 

 

OSC to CSS, http://addons.oscommerce.com/info/7263 -Mail Manager, http://addons.oscommerce.com/info/8120

Share this post


Link to post
Share on other sites

If you put a <head> on each page, then it is quite useful to also do this:

 

in application_top.php put something like this somewhere:

$doctype='<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">';
$stylesheet='<link rel="stylesheet" type="text/css" href="css/stylesheet.css">
<link rel="stylesheet" type="text/css" href="templates/'css/superfish.css">
<link rel="stylesheet" type="text/css" href="templates/'css/prettyphoto.css" />              
<script type="text/javascript" src="includes/javascript/jquery.js"></script>		
<script type="text/javascript" src="includes/javascript/prettyphoto.js"></script>
<script type="text/javascript" src="includes/javascript/superfish.js"></script>  		
'; 

 

Then each catalog page you have this:

 

echo $doctype;
?>
<head>
<?php echo $stylesheet;


Oscommerce site:

 

 

OSC to CSS, http://addons.oscommerce.com/info/7263 -Mail Manager, http://addons.oscommerce.com/info/8120

Share this post


Link to post
Share on other sites

If you put a <head> on each page, then it is quite useful to also do this:

 

in application_top.php put something like this somewhere:

$doctype='<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">';
$stylesheet='<link rel="stylesheet" type="text/css" href="css/stylesheet.css">
<link rel="stylesheet" type="text/css" href="templates/'css/superfish.css">
<link rel="stylesheet" type="text/css" href="templates/'css/morejs.css" />              
<script type="text/javascript" src="includes/javascript/jquery.js"></script>		
<script type="text/javascript" src="includes/javascript/morejs.js"></script>
<script type="text/javascript" src="includes/javascript/superfish.js"></script>  		
'; 

 

Then each catalog page you have this:

 

echo $doctype;
?>
<head>
<?php echo $stylesheet;

 

There is nothing special about those stylesheets, it's just an example of how you can stack up endless references.


Oscommerce site:

 

 

OSC to CSS, http://addons.oscommerce.com/info/7263 -Mail Manager, http://addons.oscommerce.com/info/8120

Share this post


Link to post
Share on other sites

OK, in the pseudocode example I gave, you'd do this;

 

the existing template_top is (portion of);

 

<head>
<meta http-equiv="Content-Type" content="text/html; charset=<?php echo CHARSET; ?>">
<title><?php echo tep_output_string_protected($oscTemplate->getTitle()); ?></title>
<base href="<?php echo (($request_type == 'SSL') ? HTTPS_SERVER : HTTP_SERVER) . DIR_WS_CATALOG; ?>">
<link rel="stylesheet" type="text/css" href="stylesheet.css">
<link rel="stylesheet" type="text/css" href="ext/jquery/ui/redmond/jquery-ui-1.8.4.css">
<script type="text/javascript" src="ext/jquery/jquery-1.4.2.min.js"></script>
<script type="text/javascript" src="ext/jquery/ui/jquery-ui-1.8.4.min.js"></script>
<?php echo $oscTemplate->getHeaderTags(); ?>
</head>

 

So, to add the bits you wanted, ONLY on product_info, you -could- do this;

 

<head>
<meta http-equiv="Content-Type" content="text/html; charset=<?php echo CHARSET; ?>">
<title><?php echo tep_output_string_protected($oscTemplate->getTitle()); ?></title>
<base href="<?php echo (($request_type == 'SSL') ? HTTPS_SERVER : HTTP_SERVER) . DIR_WS_CATALOG; ?>">
<link rel="stylesheet" type="text/css" href="stylesheet.css">
<link rel="stylesheet" type="text/css" href="ext/jquery/ui/redmond/jquery-ui-1.8.4.css">
<script type="text/javascript" src="ext/jquery/jquery-1.4.2.min.js"></script>
<script type="text/javascript" src="ext/jquery/ui/jquery-ui-1.8.4.min.js"></script>
<?php
if (basename($_SERVER['SCRIPT_FILENAME']) == FILENAME_PRODUCT_INFO)) {
  ?>           
<script type="text/javascript" src="includes/javascript/prettyphoto.js"></script>
<script type="text/javascript" src="includes/css/prettyphoto.css"></script>    
  <?php
}
?>
<?php echo $oscTemplate->getHeaderTags(); ?>
</head>

 

The "if" code "sniffs" what page is being presented and if it IS product_info.php then it will load the prettyphoto.js and prettyphoto.css files. Note that I have not tested that code, it's just to illustrate the example.

 

OK, so it could get messy if you need something on product_info, something else on reviews, something else on index and so on. In that case, it would not be much work to create a new function that dynamically loads in based on getheadertags, or some self baked scripts such as sniffing if there is a folder inside modules called "FILENAME_PRODUCT_INFO", and then load any files from that folder using a glob. That's something I've done on a tool that I own that creates websites.


Help shape the future of Phoenix; join the Phoenix Club

Share this post


Link to post
Share on other sites

Ok, I feel better, and it really isn''t rocket science. (however, 'glob' sounds like science fiction). In fact, like you set it up, you could have a nice tidy file with all your javascript.

 

Wait, though, wouldn't you have to run through all the 'if (basename($_SERVER['SCRIPT_FILENAME']) == FILENAME_PRODUCT_INFO)) ' statements on each page load? It seems that would be almost as bad. You are basically using programming to overcome a issue that has a simple structural solution.

 

Their is the example of some buses they had in Brazil that would open lots of doors all along the side. People could get off and on really quick. People would pay at a turnstile and then line up along the street side that had railings on the sidewalk that would coorespond to the doors on the Bus. The problem was inventing the sensing device the bus driver could use to guide him in stopping the bus to line up just right. While the Engineers spent some time on it, the Bus drivers just painted a line out on the street that the driver could see looking down from the driver's window.


Oscommerce site:

 

 

OSC to CSS, http://addons.oscommerce.com/info/7263 -Mail Manager, http://addons.oscommerce.com/info/8120

Share this post


Link to post
Share on other sites

As I explained, to solve the problem of multiple "if" statements, we'd use the getheadertags or a different coded solution to come up with the same thing.

 

That said, running thru a bunch of "if" has negligible impact on how quickly the page is served - it just looks a bit sloppy code. Hence the use of getheadertags or similar. Glob is just a native php function that allows to collect "stuff" (could be the contents of a given folder for example)...on the php page I linked to, look at "Example #1 Convenient way how glob() can replace opendir() and friends."...and you should see an interesting possibility.

 

What you do in your osc2css contribution is not ideal. We need to strive to have a more modular solution, whereas you are going away from that. In my opinion the next version of osc2css should revert to something closer to how 2.3 is, making use of the inbuilt functions to load the js/css files needed. But that's only my opinion as an interested bystander.


Help shape the future of Phoenix; join the Phoenix Club

Share this post


Link to post
Share on other sites

I think it would be simpler to split the head tags across the template and catalog files. And it is certainly not going to slow anything down. It will be less programming. Looked at it the other way around, I would ask, what is the advantage gained in putting the full header in template_top.php. Given the choice of installing a Jquery function by pasting in references into the head or by writing conditional statements to call them out, I would rather cut and paste.

 

OSC to CSS is separate from the progamming. It is about design, styling. it is nothing more than replacing the tables with divs that can accept the full range of CSS selectors. In fact the more modular OScommerce becomes the easier it will be to write OSC to CSS. A style-sheet is a sort of modular component, a way of pulling inline styling out of the webpages. Divs are just a more flexible unit than tables, and allows you to pull more of the styling away from the programming. It in fact enhances modularization. It makes it easier to separate the code from the' fluff'. Look at any stock OSCommerce page, you go blind trying to pick the code out of the mass of tables, compare it to the same page in OSC to CSS. The code is far easier to see, and has far less html around it.

 

Your point is well taken, and I can see why it would be nice to use code to call in stylesheets and javascript to the header, it sort of helps to separate the programming from the html, but I think that particular case sucks. In any case OSC to CSS will benefit from a more modular OSC.


Oscommerce site:

 

 

OSC to CSS, http://addons.oscommerce.com/info/7263 -Mail Manager, http://addons.oscommerce.com/info/8120

Share this post


Link to post
Share on other sites

This is starting to become a osc2css conversation (which I didn't really want to enter into), rather than a 2.3 conversation. Another time maybe?

 

In 2.3, the basis is starting to work towards a better setup of files, which can only be a good thing.


Help shape the future of Phoenix; join the Phoenix Club

Share this post


Link to post
Share on other sites

You're right, some other time

 

What I would like to see with 2.3 at a minimum, is some new demo products. My wife actually got the movie, 'There Something About Mary' on netflix, and I just had some gut reaction to it. No way I was going to watch it.


Oscommerce site:

 

 

OSC to CSS, http://addons.oscommerce.com/info/7263 -Mail Manager, http://addons.oscommerce.com/info/8120

Share this post


Link to post
Share on other sites

Hello members,

 

Not sure if I can post this here. I did post my question here but was told that there isn't anything he can do for me. So hoping someone is able to assist me a bit.

 

I am trying to download this contribution version 2.0 dated for 15 Sept, 2010. I've tried the earlier full packages downloads with great success. But the latest version 2.0, I get error message trying to download it. If you read my post in the top link in this post, one can see what error I am referring. So if any member was able to download that one specific mod, and if a way to download/copy the file for me. Maybe then I can get it through another source. Never had hos problem before. I have tried several times, but all fails.

 

Thank you.

Share this post


Link to post
Share on other sites

Not sure if I can post this here.

 

Yes, I can confirm this, that's exactly the right place to post your question.

 

Very clear: You have problems with downloading an addon and the discussion here is about the new osCommerce version 2.3 that is still in development

 

I'll also post my last holiday pictures here, what do you think?

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×