Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogNotes on how to fix bugs in Blog 4.0.0 used with DNN 5.4.2Notes on how to fix bugs in Blog 4.0.0 used with DNN 5.4.2
Previous
 
Next
New Post
6/15/2010 9:22 PM
 
For clean install of DNN 5.4.2 and then install of Blog 4.0.0 and then build the web site, there is one error and multiple warnings when built in VS2010.

Here are my notes on fixing the problems so that the web site can be built without any errors from the Blog 4.0.0 module:

error is in BlogImport.ascx line 31 text property cannot be set declaratively

after fixing that error (by deleting Text attribute and value) and then rebuilding, there is another error (reported twice) as follows
Error   11   'DotNetNuke.Modules.Blog.BlogImport.Private Sub cmdImport_Click(sender As Object, e As System.EventArgs)' is not accessible in this context because it is 'Private'.   D:\Inetdev\PortalDoorsSystemDnn35VS10\PdsDnnWebSite\DesktopModules\Blog\BlogImport.ascx   73   
Error   12   'DotNetNuke.Modules.Blog.BlogImport.Private Sub cmdImport_Click(sender As Object, e As System.EventArgs)' is not accessible in this context because it is 'Private'.   D:\Inetdev\PortalDoorsSystemDnn35VS10\PdsDnnWebSite\DesktopModules\Blog\BlogImport.ascx   73  

Fixed these errors by changing the Subs in BlogImport.ascx.vb from Private to Protected, retargeting the module for ASP.net 3.5 and then rebuilding the assembly DotNetNuke.Modules.Blog

After placing the rebuilt DotNetNuke.Modules.Blog assembly in the DNN 5.4.2 website, now DNN 5.4.2 will build without errors.

Do the leaders of the Blog project plan to release a new version with this and any other necessary fixes???

PS: I don't believe the retargeting for Asp.net 3.5 is necessary to eliminate the bug, but I did it because most of DNN 5.4.2 is targeted for Asp.net 3.5.

CT
 
New Post
6/30/2010 2:26 PM
 
Nice catch.

Thanks for saving my time.

Dwayne J. Baldwin
 
New Post
7/30/2010 4:28 PM
 
This solution is great if you install the source version of the Blog. If you install the "Install" version, you can easily fix the "Text" issue but you cannot change the signature of the method to protected as you don't have access to the code behind. I guess I'll have to install the source code version.

I am also trying to install the Blog module version 4.0.0 that I downloaded on 7/28/2010 on DNN 5.4.4.

Can the leaders of the Blog project make this quick fix and release the the module?
 
New Post
7/30/2010 4:42 PM
 
BTW, I went to the issue tracker for this component. There is an open item (# 18158) for this issue. It as been defined as "Low" impact and is unassigned. I wonder how a "cannot compile the code" issue is considered to be low impact. How do "They" compile their module to do the development.... We'll have to wait and see and in the meantime, install the source version and make the fix ourselves. Thx CT for the solution
 
New Post
9/5/2010 1:47 PM
 
Hi, how can I get hold of the fixed install? I am not in a position to rebuild it from the source, but I need that import capability. Thanks, Franco
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogNotes on how to fix bugs in Blog 4.0.0 used with DNN 5.4.2Notes on how to fix bugs in Blog 4.0.0 used with DNN 5.4.2


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out