Website woes - Page 2

Alex · 11-01-2007, 09:00 PM

If it is the encryption software then switching composers won't work. (But dumping FP is always a good idea)

I'd still say (we discussed this before) to just dump the encryption.

FEJ · 11-01-2007, 09:58 PM

Sounds like you have two problems.

One, getting that virus cleaned, and two, FP.
I don't known if FP is still the same but it always used to add it's own extensions that made pages not work correctly on different browsers. It may have been fixed since then, but it always left a bad taste in my mouth.

I prefer eMacs, bbedit or Vim, but they are more text based as opposed to WYSIWYG. Other than that it's Dreamweaver or KompoZer

IMO there are many better choices than FP for editing.

DreadPirateRoberts · 11-01-2007, 10:31 PM

Can you send me a copy of the html (beaucare.htm)? I'd be interested to see what it looks like.

Alex · 11-01-2007, 10:34 PM

It is saved as a single long hexidecimal string. That is what the "encrypting" is, converting plain text to hexi. If I recall correctly from the last time we discussed it the reason Snowflake does this is to make it more difficult to steal the photographs on her site.

Even if you don't ultimately want to stop encoding the files in hexidecimal (though I'd still advocate that you should and find other ways to control the photos) and the changes you've made are important then you can always just upload the unencoded files from FP and have them online that way until you can get the other problem fixed.

DreadPirateRoberts · 11-01-2007, 10:40 PM

Quote:

Originally Posted by Alex

It is saved as a single long hexidecimal string. That is what the "encrypting" is, converting plain text to hexi. If I recall correctly from the last time we discussed it the reason Snowflake does this is to make it more difficult to steal the photographs on her site.

Even if you don't ultimately want to stop encoding the files in hexidecimal (though I'd still advocate that you should and find other ways to control the photos) and the changes you've made are important then you can always just upload the unencoded files from FP and have them online that way until you can get the other problem fixed.

Please excuse my ignorance, how does this keep you from doing a right click, and save-as on the photos? Aren't they still downloaded as .gif and .jpgs?

Alex · 11-01-2007, 10:42 PM

It prevents them from being indexed by the search engines. Once actually displayed in the browser nothing will really help prevent individual theft.

Anyway, that is my memory of the last conversation. Snowflake will correct if I'm wrong.

Snowflake · 11-08-2007, 09:26 AM

Okay, a follow up.

I emailed both AVG and WebCryptPro to see if the bug was AVG doing too good of a job, Yes, that was exactly so, no bugs in the two corrupted files I sent them. The encryption software had no issues with McAfee (and they run Norton themselves). So, AVG just sent me an email that they would have an update in a patch soon that would solve this problem. Hopefully it will unlock the files it has now locked.

Now comes the search for a new WYSIWYG html editor since I will be someday soon getting a new PC/MAC/Hamster and wheel apparatus.

11-01-2007, 09:00 PM	#11
Alex . Join Date: Feb 2005 Posts: 13,354	If it is the encryption software then switching composers won't work. (But dumping FP is always a good idea) I'd still say (we discussed this before) to just dump the encryption.
	Submit to Quotes

11-01-2007, 09:58 PM	#12
FEJ Living Now Join Date: Jan 2005 Posts: 563	Sounds like you have two problems. One, getting that virus cleaned, and two, FP. I don't known if FP is still the same but it always used to add it's own extensions that made pages not work correctly on different browsers. It may have been fixed since then, but it always left a bad taste in my mouth. I prefer eMacs, bbedit or Vim, but they are more text based as opposed to WYSIWYG. Other than that it's Dreamweaver or KompoZer IMO there are many better choices than FP for editing.
	Submit to Quotes

11-01-2007, 10:31 PM	#13
DreadPirateRoberts Senior Member Join Date: Mar 2006 Posts: 2,483	Can you send me a copy of the html (beaucare.htm)? I'd be interested to see what it looks like.
	Submit to Quotes

11-01-2007, 10:34 PM	#14
Alex . Join Date: Feb 2005 Posts: 13,354	It is saved as a single long hexidecimal string. That is what the "encrypting" is, converting plain text to hexi. If I recall correctly from the last time we discussed it the reason Snowflake does this is to make it more difficult to steal the photographs on her site. Even if you don't ultimately want to stop encoding the files in hexidecimal (though I'd still advocate that you should and find other ways to control the photos) and the changes you've made are important then you can always just upload the unencoded files from FP and have them online that way until you can get the other problem fixed.
	Submit to Quotes

11-01-2007, 10:42 PM	#16
Alex . Join Date: Feb 2005 Posts: 13,354	It prevents them from being indexed by the search engines. Once actually displayed in the browser nothing will really help prevent individual theft. Anyway, that is my memory of the last conversation. Snowflake will correct if I'm wrong.
	Submit to Quotes

11-08-2007, 09:26 AM	#17
Snowflake lost in the fog Join Date: Jul 2005 Location: San Francisco Posts: 7,831	Okay, a follow up. I emailed both AVG and WebCryptPro to see if the bug was AVG doing too good of a job, Yes, that was exactly so, no bugs in the two corrupted files I sent them. The encryption software had no issues with McAfee (and they run Norton themselves). So, AVG just sent me an email that they would have an update in a patch soon that would solve this problem. Hopefully it will unlock the files it has now locked. Now comes the search for a new WYSIWYG html editor since I will be someday soon getting a new PC/MAC/Hamster and wheel apparatus. __________________ Be yourself; everyone else is already taken. - Oscar Wilde
	Submit to Quotes