XML Error: Empty document at Line 1

[pigpog]

Hello Lynne and friends. :)

I did a search for help but I couldn't find an answer, so I'm writing my problem down here.

I've written a document using Lynne's information here: https://vborg.vbsupport.ru/showthread.php?t=204782&highlight=filter to filter out text speak on my forum.

I've saved the file as an .xml document.

When I go to Plugins & Products -> Manage Products -> Add/Import Product and try to upload the .xml document I created from my computer, I get the following error:

XML Error: Empty document at Line 1

Can someone please tell me where I'm going wrong? :confused:

Many thanks!

[Speysider]

You're probably importing the xml to the wrong place. If you are using the product import page, go to the plugin import page instead and vice versa.

[pigpog]

Thanks Speysider, I'm using the product import page. The plugin import page seems to only be of use once I've uploaded the product - it's uploading the product that I can't seem to do.

[Speysider]

Are you uploading the right xml to the right place?

[pigpog]

I click on the browse button to get the .xml file from my computer, and then click import. Then the error pops up.

I don't know if I should have done something else before I try to import it? I literally opened notepad, added the code Lynne produced, added in the words that I want corrected in posts, then saved it as a .xml file.

[Speysider]

You're not being asked to create an xml file...
You're asked to create a plugin, but you need to go to:
AdminCP -> Plugins and Products -> Plugin Manager -> Create Plugin

Then do as Lynne says.

[pigpog]

Thanks Speysider, I've created a plugin. :up:

However, when I then go to create a post to test it, when I click on the submit button to publish the post, I get the following error:

Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.

[Speysider]

A content encoding error can happen if you are compressing the page too much. Try disabling Gzip compression in the vBulletin Options -> Server Optimisation Settings