Jack_mcs

A new version has been uploaded with these changes:
Added statement to load the table class in the Frozen version. Correct code for php warnings. Updated for the latest shop.  

@radhavallabhSince it works in other shops but not yours, it must be something unique to yours. If you turn the addon off in admin do all of the urls work correctly? If it does, try using the Uninstall setting and then reload the shop side. Does that fix it? If not, try turning off all cache options in the settings and try again. If it still fails then the only thing I can think to do is to install it into a new, basic, shop. That should work since it works here. Then you can try it with your database and if it fails, then it is something there that is causing the problem.  

Hi @valquiria23Yes, that is valid code. However, it should not be needed. Please check your language file, like english.php, to make sure there is a statement to define CHARSET. If there is and if it is blank change it to have UTF-8, like this
define('CHARSET', 'utf-8'); It it is already there, check your includes/application_top.php file, if this is for a pre-Phoenix shop, and make sure the code to include this addon comes after the code to load the languages.
If both of the above are correct, then it would require troubleshooting to find the cause. The change you mentionrf should work but if your site uses accented characters be sure they are handled correctly by this addon.

A new version has been uploaded with these changes. Tested through Phoenix 1.0.8.6 and php 8.
Added version for Phoenix .0.8.0 and above. Changed code for php 7.4 warnings. Fixed mistake with the uninstall code. Replaced HTTP/1.x protocol checks with $_SERVER['SERVER_PROTOCOL'].  

@bholiandYes, it will work fine in that version. Just be sure to follow the installation instructions closely.

To me, the most important question is why @osCommerce-Officialrefuses to make appearance here? @Harald Ponce de Leondid the same thing and we all know what came of that. 

To me, the most important question is why @osCommerce-Officialrefuses to make appearance here? @Harald Ponce de Leondid the same thing and we all know what came of that. 

To me, the most important question is why @osCommerce-Officialrefuses to make appearance here? @Harald Ponce de Leondid the same thing and we all know what came of that. 

To me, the most important question is why @osCommerce-Officialrefuses to make appearance here? @Harald Ponce de Leondid the same thing and we all know what came of that. 

To me, the most important question is why @osCommerce-Officialrefuses to make appearance here? @Harald Ponce de Leondid the same thing and we all know what came of that. 

The older versions of oscommerce used definitions, those items with capital letters in the errors. The later versions did away with those and use actual names. So you have to replace them to get the code to work. In this case, replace
DIR_WS_MODULES with 
'includes/modules/' Note that the apostrophes are required.

I'm sure it could be done but preventing a customer from buying more seems like a bad idea. hen the customer is returned from paypal with the Express module, he is logged in if not already done and then sent to the confirmation page. I suppose you could put a note there telling them that changing the order will cause the charge to fail.
Other than that, I'm not aware of a way to stop it except for switching to the Standard module. That one only shows up on the checkout pages so the amount is final at that point.

Maybe he browses logged out, I do that sometimes. But it is a poor start, the indication was 3-4 weeks and that was 2 months ago. I hope Vadym can come back and give a new indication even if its not a fixed date.

Those items in capital letters are definitions. They appear like that when the definition is used but does not exist. As mentioned previously, most versions of this addon included those definitions in the configure files. But later version placed them in a different file or the database.
The easiest thing to do is to search the addon (all of it, not just the php files) for one of those definitions, like OPTIONS_TYPE_TEXTAREA_NAME. You should get more than one result. Check each one to be sure you have made the indicated change.
If you only get one result, then you are probably using a partial update. Some people got lazy when uploading updates to addons and would only upload changed files instead of the complete package. If that is the case, you will need to check the previous releases until you find a complete one.

I will continue to support all of my addons since I have clients that use them. Whether or not I can offer the support here is unknown at the moment. Phoenix isn't allowed here but my addons work for other versions that are allowed so I don't know where that leaves things.
As for it not working, it works fine in 1.0.8.0. I don't support minor upgrades, for free, since they come out too often and I have other things to do. This is the same for any developer, or at least it used to be. So if you want to always use the very latest version of Phoenix, you will have problems like this. You can post the problem you are having here, at least for now, and if it an easy fix I will post that. Otherwise, you will need to wait for the next release or pay for support.

The idea of DEMOS is great but to sign in and have a private viewing is crazy.
A link to a dedicated page with sign in would have been better as allocated time is not possible for all.
I don't understand the secrecy......

A new version has been uploaded with these changes:
V 1.11
Added an error message when an invalid entry is made in the Ignore Range box. Added code to stop an IP from being blocked or ignored when it is already in the other list. Added partial searching for IP's in the Show Only IP box. So entering something like 54.56. will show all IP starting with 54.56. Added an option for debug tracing. Added more google search bots to the bots array. Added an option to check blocked IP's to see if one is google since not all of their IP's follow normal rules. Added more tables to the Clear Tables tool. Added the remote host field to the VC table to help catch bad bots. Added code to record the page name instead of the parameter when the server error addon is installed (recommended) and it gets accessed. Changed the code for getting IP details to prevent failures for some IP's. Changed the code to handle incorrectly entered IP's in the block and ignore boxes. Changed the code in Monitor to greatly speed up the page load. Changed the input boxes in the header of the Monitor section to accept input by pressing enter. Changed the validate domain code since it was missing some bots due to multiple dots. Changed the install script to restore the settings when a reset is done. Changed robots.txt file in Extras to reduce size and correct some minor issues. Changed code for sending emails for hackers and spoofers to ignore customers. Corrected the emails sent for hackers and spoofers to show if the IP was actually blocked or not. Corrected the code that identifies search bots that was added in the last version. Corrected the missing text and layout in the Warning box on the Monitor page. Corrected the Ignore list checking on the shop side. It was not seeing all ignored IP's. Corrected mistakes in some of the language files that affected formatting.s Fixed mistake in email logging code that used the wrong address. Fixed mistakes in Tools->Maintenance. PRO VERSION ONLY:
Added option to delete individual emails from the email log, Pro Version only. Added a report to show the blocked countries history. Pro Version only. Added a report to allow blocking by hosts. Pro Version only. Added a report to display a log of all changes made. Pro Version only. Added an on-page indicator showing it a hacking attempt has occurred. Pro Version only. Changed the email tracking code to ignore emails from registered customers. Pro Version only. Changed the email tracking code to record the customers IP in the Ignore list to prevent accidental banning. Pro Version only. Changed option for Bad Words to delete the persons account or not. Pro Version only. Changed the code for Bad Words to validate the email address. Pro Version only. Corrected the code in the Skimmers report to handle CIDR's properly. Pro Version only. Recommendations:
Install the Custom Server Error addon. This has long been recommended but in this version of View Counter, the argument in the url that caused the 404 is displayed. This catches attempts that were previously not seen. Replace your robots.txt file with the one in the extra directory. It has a very long list of bots that will prevent unwanted traffic, in some cases. If you do this, be sure to change the url (top and bottom of file) and un-comment the bottom one. Only do this if you have a sitemap file to reference (strongly recommended).

The attached is the changed file based on the database @alix32sent me.
header_tags_fill_tags.zip

Thanks for letting me know. Glad to hear it worked.

@valquiria23The line should be
if (defined('TEXT_MAKE_BOX_SELECTION') && $box != TEXT_MAKE_BOX_SELECTION) { But the function that code is in, named GetBoxLinks, is only called from two places. One is in Box Control which, as mentioned, shouldn't be used and the other is in the AddMissingLinks function. But the latest version has that function commented out. So it might be that you are using an older version of this addon since you should not be seeing that notice.

@valquiria23That is most likely due to having enabled an infobox in Box Control.  The code only works for infoboes in shops not using modules for them. Remove those selections and you shouldn't see the warning.

Please check admin->Sitemap SEO->Settings Control and make sure there is not an entry in the Standard Boxes box. If it is empty, edit the includes/functions/sitemap.php file and change this line
if ($box != TEXT_MAKE_BOX_SELECTION) { to
define('TEXT_MAKE_BOX_SELECTION', false); if ($box != TEXT_MAKE_BOX_SELECTION) {  

A new version has been uploaded with these changes:
Changed code to fix a 7.3 compatibility problem. Changed code to fix the character conversion option. Split into a Phoenix and non-Phoenix versions. The former accomplished by files supplied by @raiwa.

Try this. Remove the last change then change this line
$string = iconv("ISO-8859-1", "UTF-8//TRANSLIT", $string); to this
$string = iconv('UTF-8', 'ASCII//TRANSLIT', $string); Also, probably not related to this, you have Ô=> O in your array. That would cause a space to be in the url causing it to fail. As mentioned previously, you should limit the conversion entry until the code is working to be sure parts of it are not causing other problems.

A new version has been uploaded with these changes:
Corrected many compatibility issues found by member @Owl Sauron 
Removed unnecessary jquery code. Found ny member @MyBookShop,