Leaderboard

Without logging visits to the old site (new code needed: maybe add something to the Query String during the redirect, and process it in new code at your new store), all you can do is guess how long people will continue to use bookmarks to the old site. Search engines should be gone within 2 or 3 months at most... maybe allow 6 months for people not to show up at the old site? Someone is bound to follow an old link or bookmark two years from now, but at some point you've got to cut your losses of maintaining a redundant site (cost of extra domain name registration, but you ought to be able to share hosting with the new store [see "add-on domain" on most servers]).

Of course, that's on the old store's site, pointing to the new store site. If you've lost access to the old site, you're probably out of luck.

So - to feed back. With help from Raiwa, I've achieved what I wanted. Static horizontal menu at top appears all the time. When you click on a category then a vertical sub-menu appears just showing the level in the category you're at. I created a new module for this, but you don't have to. You could just amend bm_categories.php and the template file (tpl_bm_categories.php). Changed the function execute() to: function execute() { global $oscTemplate, $cPath, $current_category_id; $OSCOM_CategoryTree = new category_tree(); $OSCOM_CategoryTree->setCategoryPath($cPath, '<strong>', '</strong>'); // sets cateogory tree to current level only $OSCOM_CategoryTree->setRootCategoryID((int)$current_category_id); $OSCOM_CategoryTree->setParentGroupString('<ul class="nav nav-pills nav-stacked">', '</ul>', true); // defined category title - to call in template bm_categories $category_title = $OSCOM_CategoryTree->getData($current_category_id, 'name'); $category_tree = $OSCOM_CategoryTree->getTree(); ob_start(); include('includes/modules/boxes/templates/tpl_' . basename(__FILE__)); $data = ob_get_clean(); $oscTemplate->addBlock($data, $this->group); } Then I amended the template file - to only show this when a category has been selected. <?php if (!empty($category_title)) {?><div class="panel panel-default bm-nav-categories"><div class="panel-heading"><?php echo MODULE_BOXES_CATEGORIES2_BOX_TITLE; ?> <?php echo $category_title; ?></div> <?php echo $category_tree;?></div><?php } else {return null;} ?> Of course styles etc may be different on others versions. But it seems to work, so might be helpful to others. Thanks for your help Raiwa!

This is not possible.

You can keep your products, moving from any version of osC to any other, but you'll have to compare the database structures (schemas). It's likely that you'll have to massage the old DB to be structured the same as the new, a manual operation. When moving from one version to the next one up, SQL is often provided to do this for you, but I don't think there's anything for Frozen -> Edge. I don't think there are massive changes in the DB, but there might be a few. You are aware that Edge is a moving target (unstable -- a feature added today may be gone tomorrow)? Have you thought out why you want to leave Frozen and move to Edge? Is it worth the effort? Beyond the performance improvement of BSv4 support, I'm not sure there is that much changed. If you are having problems with Frozen, be sure to apply the patches (another manual operation; see link in my signature below).

Look closely at the database to see if the tables are the same. categories, categories_description, products, products_to_categories If you use attributes also compare the corresponding tables

There are three modules included in core that have a logoff button. There are at least two more available that are "addons" (in other words, they do not come as part of the core). Explore your admin area, particularly; admin > modules > content > {install} > (and look through this list) > install one or more.

Hello @edo.script, PWA series 3.x is intended for 2.3.4.1 BS CE FROZEN. All instructions, files and references are for this version only. If your store version is a previous EDGE version, you need to know how hooks work and to be able to adapt the instructions/code references to your store. Otherwise please use the last series 2 version ( Purchase without account BS 2.5r2 ) The most important difference in FROZEN is that hooks registry is done automatically in application_top.php. But you do not need to adit this file in any PWA version. Tht's whi it is not included in the package and there is no need for it. If your store version is previous you need to add the hook registry manually like I posted befor to the page files where hooks are used. The modification in the instructions are the hook call which is the second part you need to get the hook working. Please understand that it is impossible to include accurate instructions for all BS CE versions which are out there. There are hundreds of them. The latest versions of my add ons are all for FROZEN which is the recommended actual and stable version for users which are not skilled in coding.

If your products, SEO, directory structure, etc. are identical between the two sites, and the domain name is the only difference, it's very simple. In .htaccess, RewriteEngine On Rewrite ^(.*)$ https://<www.newdomain.com>/$1 [R=301,L] This assumes everything on the old site is to be sent over to the new site. If you want only part of traffic (to the old store) to be redirected, or the old store is in a directory of its own (a good idea), it would be done a bit differently.

The new domain will be considered a new site. If you own both domains then you can implement a 301 redirect of the old domain to the new, that will preserve most of the value built up by the old domain and transfer it onto the new domain. fixed.

Hey @Smoky Barnable, Think I can help you with this too. The Express button and the Login button are two different beasts. As always please backup before making any changes and test all changes after. Express Button The Express button specifics vary depending on how you have it configured, whether it's dynamic or static. If it's static then it is an image that's loaded from paypalobjects.com but is done in the old fashioned way of <img src="https://www.paypalobjects.com/...."> so not much can be done about that other than to save the image and then upload it to your server so it's served locally which will speed up display. You'll need to change the definition for this URL found in includes/apps/paypal/languages/english/modules/EC/EC.php on line 22 approx. All of these changes are based on 5.018 of the stock osC PayPal App (not Frozen etc) From: module_ec_button_url = https://www.paypalobjects.com/webstatic/en_US/i/buttons/checkout-logo-medium.png To (as an example): module_ec_button_url = https://www.mydomainname.com/images/buttons/checkout-logo-medium.png However any auto-updates applied in the future will revert it back to stock. IF it's being loaded dynamically then it could be because it's trying to render before the page has fully loaded all resources and this is the same problem I've found with the Login button also suffers from. For the next part to work, jQuery must be called on the page before the output of this script in paypal_express.php In includes/modules/payment/paypal_express.php approx line 220 find: $string .= <<<EOD <span id="ppECButton"></span> <script> paypal.Button.render({ env: '{$server}', style: { size: '${button_size}', color: '${button_color}', shape: '${button_shape}' }, payment: function(resolve, reject) { paypal.request.post('${ppecset_url}') .then(function(data) { if ((data.token !== undefined) && (data.token.length > 0)) { resolve(data.token); } else { window.location = '${ppecerror_url}'; } }) .catch(function(err) { reject(err); window.location = '${ppecerror_url}'; }); }, onAuthorize: function(data, actions) { return actions.redirect(); }, onCancel: function(data, actions) { return actions.redirect(); } }, '#ppECButton'); </script> EOD; And replace with: $string .= <<<EOD <span id="ppECButton"></span> <script> $( document ).ready(function() { paypal.Button.render({ env: '{$server}', style: { size: '${button_size}', color: '${button_color}', shape: '${button_shape}' }, payment: function(resolve, reject) { paypal.request.post('${ppecset_url}') .then(function(data) { if ((data.token !== undefined) && (data.token.length > 0)) { resolve(data.token); } else { window.location = '${ppecerror_url}'; } }) .catch(function(err) { reject(err); window.location = '${ppecerror_url}'; }); }, onAuthorize: function(data, actions) { return actions.redirect(); }, onCancel: function(data, actions) { return actions.redirect(); } }, '#ppECButton'); }); </script> EOD; PayPal Login THE CHANGES BELOW ARE ONLY FOR THOSE WHO HAVE SWAPPED OVER TO https://www.paypalobjects.com/js/external/connect/api.js LIKE SMOKY HAS (SEE OTHER POST REGARDING PAYPAL LOGIN UPDATE In includes/modules/content/login/templates/paypal_login.php find: <script type="text/javascript" src="https://www.paypalobjects.com/js/external/connect/api.js"></script> <script type="text/javascript"> paypal.use( ["login"], function(login) { login.render ({ <?php if ( OSCOM_APP_PAYPAL_LOGIN_STATUS == '0' ) { echo ' "authend": "sandbox",'; } if ( OSCOM_APP_PAYPAL_LOGIN_THEME == 'Neutral' ) { echo ' "theme": "neutral",'; } ?> "responseType" : "code id_Token", "locale": "<?php echo $cm_paypal_login->_app->getDef('module_login_language_locale'); ?>", "appid": "<?php echo (OSCOM_APP_PAYPAL_LOGIN_STATUS == '1') ? OSCOM_APP_PAYPAL_LOGIN_LIVE_CLIENT_ID : OSCOM_APP_PAYPAL_LOGIN_SANDBOX_CLIENT_ID; ?>", "scopes": "<?php echo implode(' ', $use_scopes); ?>", "buttonType" : "CWP", "buttonShape" : "rectangle", "buttonSize" : "md", "fullPage" : "false", "containerid": "PayPalLoginButton", "returnurl": "<?php echo str_replace('&amp;', '&', tep_href_link(FILENAME_LOGIN, 'action=paypal_login', 'SSL', false)); ?>" }); }); </script> And replace with: <script type="text/javascript" src="https://www.paypalobjects.com/js/external/connect/api.js"></script> <script type="text/javascript"> $( document ).ready(function() { paypal.use( ["login"], function(login) { login.render ({ <?php if ( OSCOM_APP_PAYPAL_LOGIN_STATUS == '0' ) { echo ' "authend": "sandbox",'; } if ( OSCOM_APP_PAYPAL_LOGIN_THEME == 'Neutral' ) { echo ' "theme": "neutral",'; } ?> "responseType" : "code id_Token", "locale": "<?php echo $cm_paypal_login->_app->getDef('module_login_language_locale'); ?>", "appid": "<?php echo (OSCOM_APP_PAYPAL_LOGIN_STATUS == '1') ? OSCOM_APP_PAYPAL_LOGIN_LIVE_CLIENT_ID : OSCOM_APP_PAYPAL_LOGIN_SANDBOX_CLIENT_ID; ?>", "scopes": "<?php echo implode(' ', $use_scopes); ?>", "buttonType" : "CWP", "buttonShape" : "rectangle", "buttonSize" : "md", "fullPage" : "false", "containerid": "PayPalLoginButton", "returnurl": "<?php echo str_replace('&amp;', '&', tep_href_link(FILENAME_LOGIN, 'action=paypal_login', 'SSL', false)); ?>" }); }); }); </script> Again, any changes made to the above files will be overwritten if the PayPal auto-update button is used at anypoint in the future.

@pete2007 it sure is (but don't tell burt I told you this or he'll get all "Stack Overflow" on me!!). Again, anyone else reading this, this is method is specific for pete2007's installation which doesn't make use of Header Tags modules nor $oscTemplate->getBlocks('footer_scripts'); and everything is hardcoded in template_bottom.php In ext/jquery/main.js find: /* BOF Prevent multiple form submissions from multiple clicks on checkout_confirmation.php */ if($('form[name=checkout_confirmation]').length > 0){ $('form[name=checkout_confirmation]').submit(function(){ Replace with: /* BOF Prevent multiple form submissions from multiple clicks on checkout_confirmation.php and contact_us.php */ if($('form[name=checkout_confirmation], form[name=contact_us]').length > 0){ $('form[name=checkout_confirmation], form[name=contact_us]').submit(function(){ And then just for the sake of completeness find: /* EOF Prevent multiple form submissions from multiple clicks */ And replace with: /* EOF Prevent multiple form submissions from multiple clicks on checkout_confirmation.php and contact_us.php */ The only caveat is that it will only display one message i.e. "Loading please wait", might have been nicer to have "Sending please wait" for the contact form. But if you want you could change it to just "Please wait" which would apply equally to both forms nicely.

In bm_category.php use: $category_titel = $OSCOM_CategoryTree->getData($current_category_id, 'name'); You just have to add a check if $current_category_id is not empty or zero and use MODULE_BOXES_CATEGORIES_BOX_TITLE for that case.

This will be down to you beeing on a shared server, looks like your host as turned on SSL on the server, just check you config file in admin/includes and make sure all http statments are changes to https. You will need to check this for every link in your code as any that still call http will cause problems of mixed content.

For the code I posted, use $keywords = preg_replace('/[^ \w-\'\"]/', '', $_GET['keywords']);

@ArtcoInc I think the link to your review is very relevant to the thread - and the threat of this hack attempt (I can’t recall the level of detail in your review but maybe you’d update to include this potential risk).

@greasemonkey (while off topic regarding hack attempts ...) I also reviewed that search add-on here ... M

Your host ought be able to tell you if you're on some spam blacklist. They may even tell you that they added you because you sent out too many emails in a short period. They don't want their servers listed as spammers, either. It's fine to email newsletters from your shop's domain, but it should probably be left to a proper bulk email application that knows how to obey host limits for per-minute, per-hour, per-day mailings. It should also try to distribute evenly and at a polite rate to major email systems like gmail, hotmail, yahoo, etc., so they don't feel overwhelmed and report you as a spammer. Do you really need to get all 5000 emails out within one hour? How about over 2 days or so? Needless to say, all mass mailings must be explicit "opt in", and should include a reminder that the recipient signed up to receive them, and a reminder on how to easily unsubscribe. The latter two items reduce the chances that a recipient will report you as a spammer, simply to stop receiving mass mailings from you.

Fake accounts with google as company name? Check here https://forums.oscommerce.com/topic/492566-fake-accounts/?do=findComment&amp;comment=1781581

Well talk to your host, many like Go *******dy will have limits set for number of emails sent per min/hour/day..... So deppending on how many you sent you may have been black listed. Talk to you host and find out. Personaly never been a big fan of ecarts beeing used for mass mailing too risky as you may get your domain black listed, much better to use a proper email marketing tool or services, mail "monkey" 😊 or some other you have many to select from, they are designed for this type of mass mailling work.

It is a redirect so just test this by removing commeting out code in .htaccess file. Then check if it works. Also check if your normal admin login works, if it does then remove the new admin and clear cache and sessions and carfully make new admin and check again.

@puggybelle I had an attack on one of my sites yesterday ... I also have a Keyword Search Report on this site. I hadn't checked it in a while, but after reading your post, I went to check it out. Guess what? Same thing here ... That's just part of one page! There are over 20 pages of this! Thank you for reporting this ... I wouldn't have thought to look at this. Malcolm

Now I found another bug. When you add a link to aproduct or a category in the slide, it doesn't work in an EDGE version, since FILENAME_PRODUCT_INFO and FILENAME_DEFAULT wasn't changed. To fix it, go to the template file of every module and change $link_slide = tep_href_link(FILENAME_DEFAULT, 'cPath=' . $url_2); } else if ( $url_1 == 'p' ) { $link_slide = tep_href_link(FILENAME_PRODUCT_INFO, 'products_id=' . $url_2); To $link_slide = tep_href_link('index.php', 'cPath=' . $url_2); } else if ( $url_1 == 'p' ) { $link_slide = tep_href_link('product_info.php', 'products_id=' . $url_2); Also, I suggest to create a directory inside catalog/images to keep all slides together. In my case, I have them inside catalog/images/banners

I think that @BrockleyJohn is right. Resolve the logging out problem first.

Of course it's possible! It sounds like you have much bigger problems than discount codes.