This is probably elementary, but we are relative novices, and haven't done a site with an RSS feed before.

When our server made our site live, (http://www.vlhnet.org/) they created a new folder and moved the concrete5 folder to a higher directory. This has created broken links to our rss feed from our blog to other places on our site. The RSS feed was working perfectly on the temp site, by the way. This is what happens now:

In Chrome: I edited the page list, selected "provide rss feed", saved that, then go to the blog llst, scroll down to the rss icon where it says to subscribe to rss feed, I get this error: Fatal error: Call to a member function getBlockTypeHandle() on a non-object in /hsphere/local/home/vlhnetorg/vlhnet.org/concrete/blocks/page_list/tools/blog_rss.php on line 13

In Firefox: when performing the same actions, it does take me to a page that says "subscribe now." But, when I copy that url, and place it into "feed url:" in another "edit rss displayer" block, I get "Oops, it looks like you've entered an invalid feed address!"

When contacting our server, who does not appear to be fond of concrete5 and hasn't worked with it much before (we didn't pick the server) he said:

"I believe you have some absolute links that are still looking for the Concrete install to be in a sub folder. This is what I get when trying to access the RSS feed from the site.

“Fatal error: Call to a member function getBlockTypeHandle() on a non-object in /hsphere/local/home/vlhnetorg/vlhnet.org/concrete/blocks/page_list/tools/blog_rss.php on line 13”
Notice how it is looking for it to exist at /concrete/
You may want to check through your code/database and remove the mention of that sub folder."

We see two "/concrete/" folders and we don't know which one to delete, as they seem identical. One is inside the concrete 5.6.3.3 folder and one is outside. We lean to deleting the one to outside the folder but really don't want to go around deleting concrete folders without some help!

I have attached a screen capture of Filezilla, one of what we see on line 13.

We feel like this is the server's issue, but since he doesn't seem inclined to help us further, and the site is now live, we need to fix this ASAP. In the string above we see /vlhnetorg/ and wonder if that is relevant at all, since the site name is next and is correct with the dot between vlhnet and org.

Thanks for any help at all!