TweezerMan

Welcome to the forums, Bompa!

It could be - searching Google for "wordpress magic_quotes_gpc" turns up a number of link to pages discussing issues like what you're describing. The PHP manual indicates that 'php_flag' should be used to set the magic_quotes_gpc setting in an .htaccess file instead of 'php_value': >php_flag magic_quotes_gpc off ...but I guess the server doesn't complain if you do use php_value. You may also see suggestions to set magic_quotes_runtime to 'off' as well. You can indeed do this in your .htaccess file: >php_flag magic_quotes_runtime off ...but this particular setting is already turned off on TCH servers.

I don't use phpBB, but from what I understand, you need to click "Go to Administrator Panel" link at the bottom of the page and log in a second time to access the admin panel. Questions about phpBB are best posted to the Scripting Talk forum.

I am not aware of any, but I don't really know much about this particular subject. I have to admit I'm at a bit of a loss to understand how or why you'd have 2 PHP scripts running at the same time that needed to communicate with each other on the server. I think you could do what you want with the methods you describe (file or database I/O), if there are no other options available on the server.

Welcome to the forums, harvey_s! Yes, you can place a different index.html file in each subdomain's subdirectory. Whether you place an index.html file in the public_html file is up to you. I'd sugeest putting one in there, just so visitors who browse to the main domain would see something other than a directory listing or a 404 / 403 error page, but the choice is yours.

Welcome to the forums, free=good!

Welcome to the forums, Birgiteqoa!

I downloaded and installed the Tags plugin yesterday just so I could see what you were talking about. I only tried it out on the Main Index template so I could see how it worked, then I uninstalled it. The Individual Entry Archive template already has an entry context, so you would not use the MTEntries and /MTEntries tags that I have in my example. On all other templates you want to use Tags plugin tags in, you would need to make sure the MTEntryTags container tags are inside of a set of MTEntries tags (like the example I posted).

You said earlier that you were using the plugin tags on your Main Index template. Assuming you are, are the plugin tags within a set of MTEntries tags? ><MTEntries lastn="7"> <MTEntryTags> <$MTTagName$> - <$MTTagDescription$><br /> </MTEntryTags> </MTEntries> At the point in the code where your error is occuring, it looks to me like the error is being caused by the MTEntryTags plugin tag not being in an MTEntries context in your Main Index template.

Yes, MT looks for its plugins in the /plugins subdirectory of whatever directory mt.cgi is in. There is an option in mt.cfg (MT 3.x) that allows specifying a different plugins directory, but most plugins don't look at the mt.cfg setting and just assume they are installed in the /plugins directory. Nope, you were 100% right on this one, Marie!

Welcome to the forums, Minkoff! Server resources include CPU load, RAM, bandwidth, disk space, etc. The different types of server resources often don't have a direct correlation with each other - an account can cause excessive CPU load while using relatively normal amounts of bandwidth. On a shared hosting server, one user who is consuming excessive CPU resources will negatively impact all of the other users on the server. TCH has little choice but to immediately suspend an account that is using excessive CPU resources, so all of the other users on the same server do not suffer a loss in performance on their sites. If you purchase a plan with 35GB of bandwidth per month, you will get 35GB of bandwidth per month. But this is not a license or permission to generate excessive CPU loads on the server.

The "Configure Active Plugins" section on the main mt.cgi will appear below the list of your weblogs only if you have at least one MT3 plugin installed. SCode is not an MT3 plugin, but Tags is, so the "Configure Active Plugins" section should be displayed, with the Tags plugin listed in it. The fact that it does not indicates that the Tags plugin is probably not installed correctly. Another way to verify this would be to look at the "View Source" from your weblog's main index page. You should see a closing /MTEntryTags tag in the HTML source code, and this is another indication that the Tags plugin is not properly installed. You might also take a look at the MT Activity Log and see if any errors are reported there relating to the Tags plugin. Assuming that you're installing the plugin file to the correct location (plugins/tags/tags.pl), I'd suggest re-uploading the tags.pl file, making sure to upload it in ASCII mode and that the uploaded file overwrites the existing one on the server.

The perl plugin file should have been installed to plugins/tags/tags.pl. The "entry file" is a replacement "Edit Entry" template, and it should have been installed to wherever you've configured MT to look for alternate template files. If you're using MT's dynamic publishing, the PHP plugin files should have been installed to the php/plugins directory. (If you're not using MT's dynamic publishing, the PHP plugin files do not need to be installed.) I tested the Tags plugin, and this code worked for me on the Main Index template, within a set of MTEntries tags: ><MTEntryTags> <$MTTagName$> - <$MTTagDescription$><br /> </MTEntryTags> You're going to have to provide more specific details about what you're doing. Where did you enter the tag? Was the "Keywords" field on your Edit Entry template changed to "Tags"? I'm not sure what you mean by "enclose the MTTagName field in quotes" - there is no "MTTagName" field on the Edit Entry template. As near as I can tell, there is no problem with the plugin that would cause the behavior you're seeing. This leaves me with the conclusion that 1) the plugin is not installed correctly, or 2) you're not using the plugin tags correctly in your Main Index template. Does the Tags plugin show up in the list of plugins on the main mt.cgi page under "Configure Active Plugins"? If it does not, then it is not installed properly. That's about all I know to tell you without more info and detail from you.

TCH is owned by the Head Guru (see his welcome above in this thread), and there is no chance that TCH will be sold any time soon (or not so soon).

PHP's shared memory functions are not enabled on TCH's servers. I presume this is because functions like these are not safe in a shared hosting environment (one user could conceivably hose the entire server).

It has been stated before on these forums that TCH does not support server-side Java, so I don't believe you'd be able to install and run StatCVS-XML on your account.

Welcome to the forums, Julie! I would recommend upgrading from Berkeley DB to MySQL before moving your account to TCH. There have been issues with taking a Berkeley DB database from one server and trying to use it on another server due to different versions of Berkeley DB in use. If you happened to encounter this issue, it would be very difficult to work around. To convert your database from Berkeley DB to MySQL, you need to have the mt-db2sql.cgi script on your server to do the actual conversion, then follow these instructions from the MT manual: Converting your Berkeley DB database to a SQL database Once you've upgraded your database to MySQL, you could then migrate your database to TCH by performing a MySQL database export (this may be available in your GoDaddy CPanel), or by submitting a ticket to the TCH Help Desk and asking them to perform a CPanel site-to-site copy to copy your entire site from your account at GoDaddy to your new TCH account. I would not recommend using MT's Export feature to export your MT database from GoDaddy because: 1) MT's Export feature only export entries, comments, and trackbacks. Your templates are not exported, and if you don't manually make a copy of them and save them to be manually installed later, they will be lost. 2) MT's Export feature does not preserve entry ID numbers in the MT database. If you export your entries with MT's Export feature from GoDaddy, then import them into a database on your TCH account, the entry ID numbers will change and cause most (if not all) of your permalinks to be broken. After upgrading your database to MySQL and migrating your site to TCH, you could then look at upgrading from MT 2.64 to MT 3.17 (currently the latest version) on your TCH account. The instructions for how to upgrade MT are also in the MT manual. Hope this helps...

Welcome to the forums, danielkerr!

Welcome to the forums, cneal!

Welcome to the forums, divinepirate!

Welcome to the forums, lightman! You'd have to have the Help Desk look at your server to know is really installed on it. I looked at my server, and while it does technically have Aspell installed, I'm not sure if what's installed could be used with SMF, or that I'd want to use it. The current version of GNU Aspell appears to be 0.60.2. The version of Aspell installed on my server is 0.33.7.1 alpha. As noted on "The Old Aspell/Pspell" page, the 0.33.7 release of Aspell is an old, dead version that is longer supported or in active development. As far as dictionaries, only the English dictionary was provided with Aspell 0.33.7. Other dictionaries are available (including Italian), but I don't know if they were part of the package installed on the server or not. My first concern about Aspell would be "what is the minimum version of Aspell that will work with SMF", then look at possibly getting additional dictionaries installed if needed. I think you mean the max_input_time setting. It is not specifically documented what a setting of "-1" does, but assuming it works like other PHP settings, "-1" would indicate "no limit". The memory_limit is not available unless PHP was compiled with the --enable-memory-limit option. It appears that PHP is not compiled with this option on TCH servers. I don't know what the server does if the --enable-memory-limit compile-time option is not used. The server may use the default memory_limit of 8MB, or it may not impose any memory limit at all. You can set this option in your .htaccess file on the server to whatever value you think is appropriate: >php_value upload_max_filesize 5M When the upload_temp_dir setting is not set, PHP will use the system's default temp directory, which I believe is /tmp. I'll have to let someone who knows for sure answer this one.

Welcome to the forums, lanys!

Welcome to the forums, Michael!

Welcome to the forums, Mae!

Welcome to the forums, snowboardmommy! I'm going to let someone else who is more familiar with SSL than I am answer these questions. You are correct - there are no additional costs or fees for accounts created within your reseller account.