Latest News: (loading..)

Archived

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

scandic_outlet

OsCommerce v 2.3 - when?

374 posts in this topic

This is probably of no interest to anyone bar me as I live in the @rse end of nowhere, or perhaps the black hole of internet access whereby I cannot receive: -

 

  • Land line based broadband
  • Mobile broadband ( GPRS nor 3G )

I have to rely on a horrible wireless local network.

 

Therefore when I have internet failure ( very regular ) I fall back on developing on my local PC server. If the site I am working on includes offsite files via http then I am scuppered.

 

I think a nice little "inclusion factory" for javascript libraries, jQuery and UI friends would be great .. except for me that is :)

 

If jQuery only maybe not a factory but a singleton with a chained load method like ..

 

jQuery_Inclusions::instance()
->load( 'jquery-1.4.2.min' )
->load( 'jquery-ui-1.8.5.custom.min' );

Share this post


Link to post
Share on other sites

Loading jQuery from Google's servers brings in no disadvantages when the Google Analytics header tag module is enabled. In fact, jQuery could also be loaded through a header tag module with an option to load the local jQuery library or the library hosted by Google. A second parameter could also be added to load a specific jQuery UI theme.

 

Overkill or not?

Is there an advantage to loading JQuery from Google servers? It seems to be a good idea for the reasons stated in the link posted above by Pronux.

 

However, when I have the Google analytics references in the header ( of 2.2RC2a) I get the annoying popup in IE that 'some stuff on this page is insecure, do you wish to continue, etc, etc.' and that issue goes away when I don't use the references to Google's servers. I'm I missing something? Or is there something in the 2.3 GA header tags module that is not in 2.2 that would fix this?

 

Thanks.

Share this post


Link to post
Share on other sites

Hi George..

 

However, when I have the Google analytics references in the header ( of 2.2RC2a) I get the annoying popup in IE that 'some stuff on this page is insecure, do you wish to continue, etc, etc.'

 

You must be using an Add-On as that is not a core feature on v2.2. It is a core feature in v2.3 as a header tag module, with the module using the standard Google Analytics javascript code that detects the http/https protocol, with something like:

 

ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';

 

The scenario you are experiencing should not occur under v2.3.

 

Kind regards,

Share this post


Link to post
Share on other sites

Is there an advantage to loading JQuery from Google servers? It seems to be a good idea for the reasons stated in the link posted above by Pronux.

 

However, when I have the Google analytics references in the header ( of 2.2RC2a) I get the annoying popup in IE that 'some stuff on this page is insecure, do you wish to continue, etc, etc.' and that issue goes away when I don't use the references to Google's servers. I'm I missing something? Or is there something in the 2.3 GA header tags module that is not in 2.2 that would fix this?

 

Thanks.

 

In these cases your code to include the file from Google should detect whether the scheme is HTTP or HTTPS and load the file accordingly .. Google host file in both schemes.

Share this post


Link to post
Share on other sites

What I am doing that is causing the issue is placing this reference or similar in the header (of 2.2RC2a).

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>

 

I appreciate both your responses, I don't quite understand them well enough, however, to translate them into a workable reference to the external Google file that I can use in 2.2RC2a that won't result in that popup.

Thanks!

Share this post


Link to post
Share on other sites

Hi Robert..

 

v2.3 is still PHP4 compatible :thumbsup:

 

Kind regards,

 

Ah yes.

 

Still, I don't think it is overkill, more and more people are using jQuery UI.

Share this post


Link to post
Share on other sites

Hi George..

 

I appreciate both your responses, I don't quite understand them well enough, however, to translate them into a workable reference to the external Google file that I can use in 2.2RC2a that won't result in that popup.

 

Something like this will work:

 

<script type="text/javascript" src="<?php echo (isset($_SERVER['HTTPS']) && (strtolower($_SERVER['HTTPS']) == 'on') ? 'https://' : 'http://') . 'ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js'; ?>"></script>

 

Kind regards,

Share this post


Link to post
Share on other sites

An alternate route to load jQuery from Google might be to just setup a subdomain on your own website.

 

For example http://jslib.MYSITE.com

 

simply adjust the urls of your javascript library including the jquery and jquery ui to point there.

Share this post


Link to post
Share on other sites

Can someone please help me.

I have installed the updates etc to make OsCommerce v2.3 but I get this error

 

Parse error: syntax error, unexpected ';', expecting ')' in /home/******/public_html/*************/admin/login.php on line 53

 

The code being

(52)$admin = array('id' => $check['id'],
(53)$actionRecorder->_user_id = $admin['id'];
(54)$actionRecorder->record();

 

Yet when I make the amendment it recommends I get the following error to replace it

 

Parse error: syntax error, unexpected T_VARIABLE in /home/*******/public_html/********/admin/login.php on line 54

Share this post


Link to post
Share on other sites

I am putting this here in the hope that it will be seen.

 

It is not a bug, but is something not quite right with osCommerce v2.3

 

When a customer writes a review, the review appears instantly on the site. A guest can write any abusive or non-constructive text and particularly on larger stores, this may not be detected for some time.

 

There is a contribution to make the reviews approved by admin before inclusion, but it would be a lot simpler if this functionality was added to the new version.

Share this post


Link to post
Share on other sites

Can someone please help me.

I have installed the updates etc to make OsCommerce v2.3 but I get this error

 

Parse error: syntax error, unexpected ';', expecting ')' in /home/******/public_html/*************/admin/login.php on line 53

 

The code being

(52)$admin = array('id' => $check['id'],
(53)$actionRecorder->_user_id = $admin['id'];
(54)$actionRecorder->record();

 

Yet when I make the amendment it recommends I get the following error to replace it

 

Parse error: syntax error, unexpected T_VARIABLE in /home/*******/public_html/********/admin/login.php on line 54

 

I'm guessing here, but looks to me like you need to ADD the closing bracket before the final semicolon on line 53

 

(52)$admin = array('id' => $check['id'],
(53)$actionRecorder->_user_id = $admin['id']);
(54)$actionRecorder->record();

 

If written as one continuous code it would then be -

 

$admin = array('id' => $check['id'], $actionRecorder->_user_id = $admin['id']);

 

which would then be a logical code line with the brackets opened and closed properly and the php line ended with a semicolon.

 

Let me know if it works.

Share this post


Link to post
Share on other sites

I am putting this here in the hope that it will be seen.

 

It is not a bug, but is something not quite right with osCommerce v2.3

 

When a customer writes a review, the review appears instantly on the site. A guest can write any abusive or non-constructive text and particularly on larger stores, this may not be detected for some time.

 

There is a contribution to make the reviews approved by admin before inclusion, but it would be a lot simpler if this functionality was added to the new version.

 

+1 Add my voice to that.

There should be an inbuilt method for admins to review and approve/disapprove anything that users add to a store.

Share this post


Link to post
Share on other sites

Hi, presently I have a store built on RC2a with about 12 addons plus my own developed.

Further more, I have fixed all bugs I could find (officially known and unknowns) both to the core and the addons.

(This required restructuring of parts of the core code).

And, I have both admin- and catalog side fully w3c-validated. I even took the time to correct js scripts like the spiffycal.

Also, I have a security level which is "good enough".

 

The only caveat I have left is with the "Ajax Attribut Manager", it's not multilingual although so stated.

(I am trying to fix it).

 

So, all in all I am very reluctant to move to v2.3 if not someone can give me at least 3 very, very good reasons.

Especially since there are continous bug reports coming in.

 

Try to persuade me to move to v2.3, if you can... give me the reasons...!

 

Sara

 

demo: www.ji-fashion.com

 

client: www.tyraochsally.se

Share this post


Link to post
Share on other sites

(52)$admin = array('id' => $check['id'],
(53)$actionRecorder->_user_id = $admin['id'];
(54)$actionRecorder->record();

The correct fix is

$admin = array('id' => $check['id']);
$actionRecorder->_user_id = $admin['id'];
$actionRecorder->record();

The second line is setting an object's local variable to a value, and the third line is invoking an object's member function.

Share this post


Link to post
Share on other sites

+1 Add my voice to that.

There should be an inbuilt method for admins to review and approve/disapprove anything that users add to a store.

The only usable user feedback system would either

1) hold all submissions for review before being posted, or

2) disable HTML tags (at least, dangerous ones), scan for obscenities and banned words and spam, and provide a reporting mechanism for other readers.

 

A feedback or review system that doesn't provide either (or both) methods is dangerous and should be disabled.

Share this post


Link to post
Share on other sites

The only usable user feedback system would either

1) hold all submissions for review before being posted, or

2) disable HTML tags (at least, dangerous ones), scan for obscenities and banned words and spam, and provide a reporting mechanism for other readers.

 

A feedback or review system that doesn't provide either (or both) methods is dangerous and should be disabled.

 

 

Well HTML tags have been disabled with the review system but it really would be better if the reviews were held for approval and not just posted directly on the store as the possibility for abuse, spam etc is quite high.

Share this post


Link to post
Share on other sites

Ok, Since this thread has gone in many directions since it was originally posted on Sept 13, 2010. Let's ask the original question:

 

WHEN WILL V2.3 BE RELEASED ?

 

It's a simple question and is deserving of a FIRM release date. Almost two months have passed since it was originally asked, yet NO answer has ever been posted.

 

 

Let's get v2.3 released and close the books on the 2.x series so time and effort can be focused on v3.x. The development team is much too slow and should consider involving more eager programmers that are almost begging to help.

 

 

JMO

 

 

Chris

Share this post


Link to post
Share on other sites

Well, If you take a look at github, it is obvious that Many changes are being made on a daily basis. Version 2.3 looks like it will be a lot more modern that the crusty old version. I would rather see something complete instead of a half baked and rushed solution.

 

That said, in my opinion, It would be great of osCommerce did a talent recruitment in order to help speed up the process and properly market the new version. It really has the feel of a very closed project where we can all chit chat on the forums but there does not seem to be any great desire to involve members and use their talents more.

 

Mark

Share this post


Link to post
Share on other sites

Hi Sara..

 

Hi, presently I have a store built on RC2a with about 12 addons plus my own developed.

Further more, I have fixed all bugs I could find (officially known and unknowns) both to the core and the addons.

..

Try to persuade me to move to v2.3, if you can... give me the reasons...!

 

It looks like you're already rocking! Why upgrade? You can keep building on what you have and continue to use v2.2 add-ons.

 

Kind regards,

Share this post


Link to post
Share on other sites

Well, If you take a look at github, it is obvious that Many changes are being made on a daily basis. Version 2.3 looks like it will be a lot more modern that the crusty old version. I would rather see something complete instead of a half baked and rushed solution.

 

 

I have to agree with Mark, I see 2.3 has come a long way. The members working on this is doing a great job. I am no program-er and so I always look for help/comments here in this forum. I for one, would love to see tabs incorporated into 2.3. I have been working with the new 2.3 on my hard drive to see what can be done. I do see header tags is in it's folder, but when viewing the source code, I do not see any meta tags for title, description or the keywords. So is this something to enable first?

 

Please forgive me if went over board in this post or even posted this in the wrong thread.

Share this post


Link to post
Share on other sites

I am not sure how many people are aware of this excellent ( oscommerce ) documentation here:

http://www.oscommerce.info/confluence/display/OSCDOC22/Upgrade+Guide

 

The changes to V2.3 are all good. I have applied all changes except the template and header tags implementaion, which no doubt is the biggest change. But if you have a settled store then that is too much work for too little benefit in my opinion. V2.3 gives you header tags for the homepage, cats, and manufacturers, but it is not clear how you will get title tags for your other pages without adding some code. I also don't like the fact that you cannot easily make changes to the head section of individual pages anymore.

 

As far as I am concerned, my store is moved to V2.3 without the template system and header tags. The only problem with this is that any future updates or fixes released here, may assume the templating system of V2.3.

Share this post


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