LisaJill

I'm not sure, as far as I know you have to go through cpanel or phpmyadmin. The server is generally "localhost" and the databases are not shared, you get your own (unlimited number) of them. =) I would personally suggest a database import, it's the easiest thing to do. Make sure that you have downloaded and upload the files here (especially the templates) if you have done any customizations and/or hacks. =)

No, it's just not finding it there. Do you mind posting the url, or can you pm me with it? I'll have a look. =)

Dan, the vti files are frontpage extensions. If you don't use frontpage you can uninstall the extensions via cpanel and those files will go poof. If you used cpanel on your old host and still have access you can submit a ticket and ask the tech guys to move it over. This won't always work, it depends on the setup on your old hosts site. If you don't/can't do that - then a mysql export and re-import here is the easiest way. You'll still need to upload the program files to run it, of course. Hope that helps. =)

try /home/username/public_html/easymoblog/batch/easymoblog_batch.php let me know how that works. =)

If the msql screen isn't showing those database there mayb e a permissions problem somewhere. I'd suggest you submit a ticket (top of the page) to have it investigated. =)

Please submit a ticket about this. There is a link at the top of the page for the Help Desk. Thank you. =)

the host will be localhost did you create the database AND add your user to the database? the database name will be something like cpanelname_dbname - and your username will be cpanelname_whateveryouchose =) with password being just the password you chose. sometimes people forget and leave off the cpanelname_ and that causes problems. Let me know if that helps =)

Also, if they sent that exact same email to me, they'd use scripts that would make it look as if it is from me to me. No manual labor added. Just ignore them. =)

1) The cost is per domain hosted at TCH. If you host the domain elsewhere and just park it here there is no extra charge. 2) There is a cap on emails sent out. I forget what the numbers are - but you can set mailman to automatically distribute the emails so that you don't go over that limit. 3) Unlimited mysql databases for all plans. 4) Unlimited - what it says is what you get. =)

I would look through hotscripts.com for one, but I'm not familiar with the scripts offhand. Maybe someone else where uses one and can suggest it. =)

It is, MoonFaery, but it's 100% worth learning for sure. It's much more elegant and easier in the longrun, I think. =) and free'er.

-- Georg Groddeck (1866-1934), German psychoanalyst. The Book of the It, Letter 32 (1923). Good luck to you, you can make it through this. =)

At the top of the forumt here is a link to submit a ticket. Just put in your details and your request and it'll be done. After they confirm it you'll need to point it out our nameservers, of course. =)

Yes, just get the first domain then submit a ticket to have it parked. As long as they both point to your site root then it's fine. =)

This has nothing to do with your domain. It's just people that use programs to insert fake information into the headers. It is highly unlikely that it is actually coming from your domain. It is very likely that it went to millions of people and it all looked like it came from the respective person. Just trash it, nothing really to be done. =/

Certainly, Bruce, and I've had a blogger account for over a year. But he asked about other solutions. =)

No, not through AWStats. You would need to go to hotscripts.com and download a link tracker. Note - you'll probably need to change the link so that it parses through the script, instructions will be in any of the scripts you download. =)

Bloglines checks last updated headers (this is not something I can explain, it's a technical issue, you can google for http headers for information) and then pulls it in if it's updated. It checks these one an hour. You do not need to republish or anything for it to do that - if they've changed it, it'll update them. You don't have to re-post anything, it'll detect the changes, it's smart and neat. And it did, as per my last post - they're fixed and showing up properly now. =)

Bloglines just re-published these and they work, now, ramone. =)

I believe thats 6:32pm - 24 hour time. =) I'm not sure what data center you're in, nor am I really all that conversant where each one is, but I'm sure someone else can help ya out. =)

I was browsing the MT forums and came across a request for a livesearch plugin. I had a look at what livesearch is and went "wow". I then immediately went and and requested an EE plugin. That was arouond 11pm last night, I think. As of right now it's live on my site. Here's the small post I made about it with links to livesearch and to the EE thread. I think this is pretty neat, cutting edge technology. Unfortunately, I don't know much about it, just enough to follow the instructions to make it work on my site. But I figured some of you would be interested in it. =)

ramone, this will probably only work for newly published entries - or if bloglines re-reads the feeds. It won't work retroactively if bloglines does not re-load the feeds, of course. Try posting a new message and see if it works. If it does not - I highly suggest you post over in the technical support forum at EE and let them help troubleshoot it - as that is about the limit of my knowledge with it and I'm fairly positive that the plugin is the problem. I'm not aware of anyone else at TCH that is that experienced (or at all) with EE so utilizing the tech guys at EE would be very useful. (I responded twice in your thread there.. I just think that you need to use the right avenue to get the most help. =) )

There was also a mention somewhere that if you are experiencing difficulties/approaching your quota restrictions for the month, you can submit a help desk ticket and they'll get it actioned faster for you. But they will check so only do this if its truly necessary. =) Part of the reason that it's being taken slowly is to ensure that the servers do not suddenly get overloaded suddenly. =)

That is correct. There is an explanation from Mike in this thread. =)

After looking at it I can say 95% that the reason it's not working is you have an old, buggy version of the XML Encode plugin. Grab the newest one and upload it to plugins and your feeds should work. =) The reason that I can tell this is that it is showing a character entity for one of the slashes (& # 4 7 ; or sometihng like that) which is what the update to the plugin fixed.