R – Blog host with importing from dotnetnuke blog

blogsdotnetnukeimport

I want to migrate my blog from my own dotnetnuke site to another host (like blogger, posterous etc). Do you know any such host that supports importing from dotnetnuke.
Posterous supports importing using MetaWebLog API, which is supposed to be supported by dotnetnuke blog module. I tried it but it does not work. I always get 'We were not able to authenticate this account' message from Posterous, altough at the same time I can post to my dnn blog using Word and MetaWebLog API.

Best Answer

I agree about moving this to superuser.com. In the meantime, here's an answer.

I am a developer on the DNN Blog module team. I have three answers:

You should stay on DNN! :)
You really need BlogML support for this to work correctly. BlogML is coming to the Blog module (timeframe TBD)
You may be able to change your RSS settings in the blog module to use RSS to solve this problem. If you DO NOT use Summaries (but instead let the module create summaries automatically) then if you change these settings in Module Options then all of your content will be served by the RSS feed:
- Limit Auto-Generated Summaries to: 0
- RSS Entries to Display: 0

I don't know why the MetaWebLog interface doesn't work for you. Possibly a compatibility issue between Posterous and the DNN MWL implementation?

Related Solutions

R – SEO consequences of using a subdomain for an externally-hosted blog

There are a lot of advantages to self-hosting your blog.

You can do whatever you want with your own self-hosted blog. On Wordpress you could get banned and lose all of your content.
You can host ads or and do other commercial stuff not possible on Wordpress. (The free wordpress blog doesn't allow any advertisements other than their own ads).
Better ranking opportunity in search engines by using your own top-level domain.
You can modify your functionality at will.
It looks more professional and gives you bragging rights.
On Wordpress you may run up against bandwidth restrictions if your blog gets really popular - you won't be able to do anything about it.

R – DotNetNuke module development with webservices

You can include the ASMX file by including a element in the <files> section:

<files>
 <file>
  <name>YourWebService.asmx</name>
  <path></path>
 </file>
</files>

Generally, you don't need to specify a path.

Alternatively, you can include a Resources.zip file with your package which will include any files other than those that DNN needs to process during installation (e.g. Assemblies and SqlDataProvider files).

The benefit of this is maintainability. Using Resources.zip will keep you from having to edit the manifest file over and over...

The contents of the zip file will simply be unpacked into the root module directory (e.g. /DesktopModules/YourModule/*). If there is a file structure within your zip file it will be maintained.

You'll want to add TheNameOfYourFile.zip To your manifest file under the element.

[snip]

<folder>
  <name>Your Module</name>
  <friendlyname>Your Module</friendlyname>
  <foldername>YourModule</foldername>
  <modulename>YourModule</modulename>
  <description>A module for DotNetNuke websites.</description>
  <version>01.00.00</version>
  <resourcefile>Resources.zip</resourcefile>
  <businesscontrollerclass></businesscontrollerclass>
  <modules>
    <module>

[/snip]

As for referencing it in your module - I suggest using:

<%=ResolveUrl("~/DesktopModules/YourModule/Services.asmx")%>

Best Answer

Related Solutions

R – SEO consequences of using a subdomain for an externally-hosted blog

R – DotNetNuke module development with webservices

Related Topic