A comment posted by graulund on Mar 23rd, 2012. View parent comment ↑ | View all comments on this thread →
As you seem to have discovered already, Tweet Nest doesn’t actually create folders in any way — the special URLs that look like a folder structure are put in place so the paths look more human readable.
This is what the .htaccess files help with in an Apache installation. Without them correctly installed, the server will actually try to look for that folder and, naturally, cry when it doesn’t find it. So this issue is usually due to these .htaccess files either being not present, not read or otherwise interfered with in some way.
The issue is complicated by the fact that the files are usually hidden on a UNIX-based system, so it can be hard to see if they are present. Then you need to make sure they are read and interpreted (see the “AllowOverride” directive in Apache config) and that the rules don’t clash with other similar files somehow (this is mostly trial and error).
I’ve heard that if you run Tweet Nest in a subdirectory of WordPress, the different .htaccess files for these two different apps collide in some way and create an issue. I haven’t been able to resolve this, though, because I don’t use WordPress myself. But it could be an idea to move it into a completely separate directory to see if that helps.
Do you know what an .htaccess file needs to include so it will work properly? I successfully uploaded a file and renamed it with the ‘.’ prefix but I don’t think it included the requisite code. I used a generic version I found online. If you or anyone else can provide a sample file to use I’ll give that a try. I loaded Twitter Nest in a new directory as an ‘add on slot’ on my hosting account, rather than a subdirectory.