The online FAQ database contains hundreds of answers to frequently asked questions, articles on using our
web server applications and other related technologies, and resolutions to common problems. If you are seeing
an error message, be sure to try searching on the error message or error number that you are seeing.
|
| |
| |
| |
| |
|
Why does XCENT's applications have all these file names that seem strange?
|
|
|
XCENT's scripting products use a naming convention that is used on all products. The file naming convention provides a way to track files, where they belong, and prevent filename collisions on your site. By utilizing the naming convention, it helps both the XCENT developers, and your own developers – if applicable, to be able to track where certain files belong and improves the ability to add to and customize the applications without accidentally creating conflicting filenames.
Contrary to some opinions, this has absolutely nothing to do with promoting the XCENT name or application. If this was the reasoning behind the filenames, we certainly would not want you to remove the XCENT names, logos, and links from the sample templates and files included with the application. However, as even the product’s license agreement states, you certainly are free to do just that. There is nothing in the license agreement that would prevent you from removing the XCENT names, logos, and links from the public user interface (*1).
The naming convention provides some level of identification. For example, when you install XcAuction Pro on your web site, any files that start with XcAP, will belong to XcAuction Pro. This helps prevent you from accidentally over-writing files with the same names. An example of how that helps is this. Say you might have a script somewhere on your site called MailToFriend.asp. With XCENT's naming convention, you will not accidentally confuse the XcAPMailToFriend.asp file with the file you have with a very similar name. This also provides some flexibility in allowing you to install multiple XCENT products in the same location on your site without overwriting important files.
If you do not want to see the filenames, an easy and simple solution is to just create a template that runs the application in a frame within your site. If you have the skill or ability to do so, the filenames can certainly be changed to suit your own purposes. However, if you do use that method, technical support will not be able to assist you with any problems you might introduce by making such changes. It is very easy to make typographical errors when writing code and support cannot diagnose any such “programming” changes you might make on your own. If you do this, we also highly recommend keeping close track of the changed filenames you use, so that you can apply any future updates if needed.
Notes
*1 – You may not remove XCENT copyright notices from the original source code. The source code is not visible to your site’s visitors, it only exists within the application itself.
|
|
|
|
| |
