MrPhil

That sounds like a call to htmlspecialchars() or maybe htmlentities() to turn < into &lt;, > into &gt;, or & into &amp; (and maybe others). That would disarm HTML tags and make them non-functional (also makes them display as-is). Many WYSIWYG editors routinely do this, although there should be a switch somewhere to suppress this for desired entries you actually want to be treated as HTML tags.

Before going off on a wild goose chase, is this the official release (from this site) or is it Edge or Frozen community-supported release (on GitHub)? I'm not sure they behave the same way WRT hooks. An add-on intended for Edge or Frozen may not work properly on the official release. Anyway, you've gone down a dead-end road if you're on the official release.

Site is up, but there are some errors listed. By the way, is this osCommerce? I looked through the source listing, and I didn't see anything familiar looking. If it's not osC, it should be removed from this forum immediately.

Please use "code" tags (or click on <> and enter your code there) so that everything doesn't get run together: Find function display_price($products_price, $products_tax, $quantity = 1) { return $this->format($this->calculate_price($products_price, $products_tax, $quantity)); } Replace with function display_price($products_price, $products_tax, $quantity = 1) { if ($products_price > 0.01) { return $this->format($this->calculate_price($products_price, $products_tax, $quantity)); } else { return 'Buy on Amazon'; } } (you were missing a }, by the way). Even better than just returning a string "Buy on Amazon", make that a link, something like return '<a href="https://amazon.com/......">' . $txt['buyOnAmazon'] . '</a>'; where you have defined a "Buy on Amazon" language string, in case you're handling more than just English. Of course, keep in mind that the link to Amazon has to be manually maintained and kept updated if it changes or goes away. I think there are some add-ons for linking to Amazon that handle this stuff for you -- you might want to check them out and see if they do the job.

How are you editing this "snippet"? Are you saying that you can successfully add it via CKeditor, but if you edit it via CKeditor, it immediately vanishes? That sounds like a bug in CKeditor if it's losing pure HTML content. Does it not immediately vanish when you save your edit, but disappear some time later? Are you able to add it back in with the CKeditor? You might want to browse the product data table in phpMyAdmin (or equivalent) to see if the HTML "snippet" truly vanished, or is still hiding in there somewhere. If you want to autoplay a video, please be considerate of your customers. At least mute the sound so that their co-workers don't get irritated by it.

OK, so what is this about? These are two fairly old add-ons. What's your point? Craig, please understand that this is not Twitter. Things work much better if you consolidate your material into one topic (thread) rather than beginning a new topic for every thought.

It is unfortunate if you based your work on the official 2.3.4.1 release, as it is totally obsolete. You may want to port your work over to 2.3.4.1BS "Frozen", or even "Edge". If all it is a Japanese language file add-on, that should not be much work. If you went and added new function, that's more work. Please respect the osCommerce license and the hard work of many people, even if you are not selling it, and consider making an add-on package that can be distributed from this site (rather than being off on some separate site). Google Translate: あなたが2.3.4.1の公式リリースに基づいていれば、それはまったく時代遅れなので残念です。 2.3.4.1BS "Frozen"または "Edge"に作業を移植することができます。 すべてが日本語のファイルのアドオンであれば、それほど大きな作業ではありません。 あなたが行って新しい機能を追加した場合、それはより多くの作業です。 osCommerceライセンスと多くの人々の努力を尊重してください。たとえそれを販売していなくても、（別のサイトではなく）このサイトから配布できるアドオンパッケージを作成することを検討してください。 Anata ga 2. 3. 4. 1 No kōshiki rirīsu ni motodzuite ireba, sore wa mattaku jidaiokurenanode zan'nendesu. 2. 3. 4. 1 BS" furōzun" matawa" Edge" ni sagyō o ishoku suru koto ga dekimasu. Subete ga nihongo no fairu no adōndeareba, sorehodo ōkina sagyōde wa arimasen. Anata ga okonatte atarashī kinō o tsuika shita baai, soreha yori ōku no sagyōdesu. OsCommerce raisensu to ōku no hitobito no doryoku o sonchō shite kudasai. Tatoe sore o hanbai shite inakute mo,(-betsu no saitode wanaku) kono saito kara haifu dekiru adoonpakkēji o sakusei suru koto o kentō shite kudasai.

I doubt that "Options -Indexes" would cause the reported symptoms. All it does is keep visitors from browsing that directory by forbidding the automatic creation of an "index" file (which lists and links to all the files in the directory) if none exists. It could cause a 500 error if your host has banned the "Options" command. Is one logged anywhere? Otherwise, I don't think that reading or writing a file in a directory would cause .htaccess to be run, but it's always possible. Yes you are. You're on the Internet, so we know.

"client denied by server configuration" can be caused by an IP block, but possibly there are other causes. The first thing is to check your .htaccess file(s) for an IP deny list, and make sure you didn't get swept up in it by accident. That's unlikely, if some accesses still get through. Then check your .htaccess file(s) for anything blocking on certain URL Query Strings that might be showing up (e.g., "edit" in the QS). Maybe your host slipped in something there without your realizing it. If that doesn't do the job, you'll have to talk with your host to see if they're blocking something upstream from you. Many hosts will IP block a visitor (upstream from your .htaccess) if an IP address is repeatedly connecting very frequently, or using a lot of time on each access. Maybe you tripped something doing bulk picture-loading page accesses. In that case, explain to your host and ask to be removed from the block list. Then be careful about spacing out your site accesses so as not to trip it again.

Being in the US, I'm not (yet) affected by this sort of thing, but it brings up an interesting point. I'm seeing more and more validation schemes and security measures being pushed on me that require a cell or smart phone (some sort of texting or SMS involved, I guess). I live in the wilds of upstate New York, and the nearest reliable cell signal is about 3 miles (5 km) down the road. I'd love to ditch my landline and just have a smart phone, but short of nationalizing telecom in order to get 100% coverage, it will probably be a while before I get service. Why can't they just have an alternate method where you can dial in and use a touchtone keypad to enter a code? Is anyone out there still actually using a rotary dial phone? Until a couple decades ago there were still some small independent phone companies in the US where you cranked the handle and asked the operator to connect you! Really.

Anything in this thread which is an enhancement request or an Edge-only bug should be moved to a different thread, or at least clearly listed here as such. Only genuine bugs in Frozen should be here, so that someone could get the Frozen release, manually fix the listed bugs, and not get tangled up in Gary's ongoing Edge work (e.g., Bootstrap v4). Enhancements should be kept out of the Frozen bug list, and leave them for Gary to put into Edge (as he wishes). Wasn't that the original intent of this thread? Maybe Gary will decide at some point to release an updated Frozen, or more likely, a new milestone for Edge ("Slushy") that incorporates all the Frozen bug fixes, plus some enhancements. In case anyone's still using Gold, bug fixes might indicate if they were for Gold only but already fixed in Frozen. Someone is going to have to decide what to do about support for older releases (Gold, Frozen [eventually]), and whether to force people to move to a recent release. Considering that some stores are still running on MS2, it's clear that some store owners are very resistant to upgrading. I don't think I would want to use pre-made patches for Frozen (say, in GitHub) that had not been inspected and approved by Gary, and that is placing even more of a burden on him. I think fixes should simply be listed here and it's the responsibility of whoever is applying them to decide that they are good. Maybe the report of a fix, supporting commentary and discussion (including fixes to the fix) could be consolidated somewhere, perhaps on GitHub?

Cyber Week and the Christmas rush... what better time to disable someone's site? Lesson learned: keep on top of domain registration, hosting, SSL cert, payment system certs, etc. expirations and put them on your calendar to take care of before they bring down your site!

I just get a little peeved at people who should know better, but don't trim out the noise surrounding/after the real bug. It's OK to mention that there were "a bunch of 'Headers already sent' messages", but to clog up the forum with unnecessary cut and paste is annoying to have to read through. Also, one copy of a real bug line with "this was repeated many times" is much better than cut & paste 500 lines of repetitions like some neophytes do. Grrr. I need another cuppa joe.

Lots of things could have gone wrong. Did you move to a different server and not update your .htaccess file's redirections and rewrites, especially if file paths (directories) changed? Did someone update .htaccess and botch the job ?