Skip to content

Commit 659642d

Browse files
authored
Merge pull request #26 from DNNCommunity/development
Merging into master for 7.2.1 release
2 parents 22005d8 + df4e9fc commit 659642d

17 files changed

+577
-361
lines changed

.github/CONTRIBUTING.md

+75
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
# How to contribute
2+
3+
Community contributions are essential part of any open source project. The
4+
community has access to a large number of unique configurations which would
5+
be extremely difficult for the core maintainers to reproduce. We want to keep
6+
it as easy as possible to contribute changes that get things working in your
7+
environment. There are a few guidelines that we need contributors to follow
8+
so that we can have a chance of keeping on top of things.
9+
10+
## Getting Started
11+
12+
13+
* Make sure you have a [GitHub account](https://github.com/signup/free)
14+
* **Submit an issue** for your issue, assuming one does not already exist. If you have the rights, you should assign yourself to the issue. If you do not have that ability please add a comment noting that a pull request will be submitted for the issue. After review, if the pull request is accepted, we will mark the issue as resolved and assign it to a release so it can be QA'ed.
15+
* Clearly describe the issue including steps to reproduce when it is a bug.
16+
* Make sure you fill in the earliest version that you know has the issue.
17+
* Fork the repository on GitHub
18+
19+
## Making Changes
20+
21+
* Create a topic branch from where you want to base your work.
22+
* This is usually the 'development' branch.
23+
* Release branches should only be targeted by official committers.
24+
* To quickly create a topic branch based on development; `git checkout -b my_contribution development`
25+
* Make commits of logical units.
26+
* Check for unnecessary whitespace with `git diff --check` before committing.
27+
* Make sure your commit messages are in the proper format
28+
* For bonus points run and add unit tests
29+
* Make sure you have added the necessary tests for your changes.
30+
* Run _all_ the tests to assure nothing else was accidentally broken.
31+
32+
33+
## Making Trivial Changes
34+
35+
### Documentation
36+
37+
For changes of a trivial nature to comments and documentation, it is not
38+
always necessary to create a new ticket in the issue tracker. In this case, it is appropriate to start the first line of a commit with '(doc)' instead of
39+
a ticket number.
40+
41+
````
42+
(doc) Add documentation commit example to CONTRIBUTING
43+
44+
There is no example for contributing a documentation commit
45+
to the DNN repository. This is a problem because the contributor
46+
is left to assume how a commit of this nature may appear.
47+
48+
The first line is a real life imperative statement with '(doc)' in
49+
place of what would have been the ticket number in a
50+
non-documentation related commit. The body describes the nature of
51+
the new documentation or comments added.
52+
````
53+
54+
## Submitting Changes
55+
56+
* Sign the [Contributor License Agreement](http://www.dnnsoftware.com).
57+
* Push your changes to a topic branch in your fork of the repository.
58+
* Submit a pull request to the DNN.Platform repository in the DNNSoftware organization.
59+
* The committers will handle updating the associated issue in the DNN Tracker to ensure it gets the necessary code review and QA.
60+
61+
## Acceptance of your Changes
62+
* We have a group of fellow developers that review pull requests submitted by developers like yourself.
63+
* If your changes look good, then changes are merged to an appropriate release.
64+
* We may ask you to make further changes or reject the change (with proper reasonsing - we hope that's not the case though).
65+
* You should get an email notification as we complete processing of your pull request.
66+
67+
## Downloading latest package with your changes
68+
* As soon as changes are accepted, our team city build server gets into action.
69+
* New builds are usually available within 10 minutes of acceptance.
70+
71+
# Additional Resources
72+
73+
* [Contributor License Agreement](http://www.dnnsoftware.com)
74+
* [General GitHub documentation](http://help.github.com/)
75+
* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)

.github/ISSUE_TEMPLATE/bug_report.md

+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
5+
---
6+
7+
## Describe the bug
8+
A clear and concise description of what the bug is.
9+
10+
11+
## Software Versions
12+
- DNN: 00.00.00
13+
- Module: 00.00.00
14+
15+
16+
## To Reproduce
17+
Steps to reproduce the behavior:
18+
1. Go to '...'
19+
2. Click on '....'
20+
3. Scroll down to '....'
21+
4. See error
22+
23+
24+
## Expected behavior
25+
A clear and concise description of what you expected to happen.
26+
27+
28+
## Screenshots
29+
If applicable, add screenshots to help explain your problem.
30+
31+
32+
## Error log
33+
**Note: Debug DLL's**
34+
Please replace the current extension DLL's with the debug DLL's (if these are available with the release) and reproduce the error with the debug DLL's before pasting the error log.
35+
36+
Paste the error log that is related to this issue.
37+
38+
39+
## Additional context
40+
Add any other context about the problem here.
41+
+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
5+
---
6+
7+
## Is your feature request related to a problem?
8+
**Please describe.**
9+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
10+
11+
## Describe the solution you'd like
12+
A clear and concise description of what you want to happen.
13+
14+
## Describe alternatives you've considered
15+
A clear and concise description of any alternative solutions or features you've considered.
16+
17+
## Additional context
18+
Add any other context or screenshots about the feature request here.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Help and other questions
3+
about: Ask for help or others questions re. using the module
4+
5+
---
6+
7+
## Please summarize your question in one sentence
8+
9+
10+
## Give a more extended description
11+
12+
13+
## Steps to reproduce (if needed)
14+
15+
16+
## Other comments or remarks

.github/PULL_REQUEST_TEMPLATE.md

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
<!--
2+
Explain the benefit of this pull request
3+
You can erase any parts of this template not applicable to your Pull Request.
4+
-->
5+
6+
### Description of PR...
7+
8+
## Changes made
9+
- Item 1
10+
- Item 2
11+
12+
13+
## PR Template Checklist
14+
15+
- [ ] Fixes Bug
16+
- [ ] Feature solution
17+
- [ ] Other
18+
19+
20+
## Please mark which issue is solved
21+
<!-- Type numbers directly after the #, it will show the issues with that number -->
22+
23+
Close #

AssemblyInfo.cs

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,6 @@
88
// </auto-generated>
99
//------------------------------------------------------------------------------
1010

11-
[assembly: System.Reflection.AssemblyVersion("07.02.00.00")]
11+
[assembly: System.Reflection.AssemblyVersion("07.02.01.00")]
1212

1313

Components/Business/AnnouncementInfo.cs

+18-10
Original file line numberDiff line numberDiff line change
@@ -360,11 +360,9 @@ public string GetProperty(string strPropertyName, string strFormat, CultureInfo
360360
case "edit":
361361
if (IsEditable)
362362
{
363-
string editUrl = Globals.NavigateURL(portalSettings.ActiveTab.TabID, false, portalSettings,
364-
"Edit",
365-
CultureInfo.CurrentCulture.Name,
366-
"mid=" + ModuleID.ToString(CultureInfo.InvariantCulture),
367-
"itemid=" + ItemID.ToString(CultureInfo.InvariantCulture));
363+
string editUrl = Globals.NavigateURL("Edit",
364+
$"mid={ModuleID.ToString(CultureInfo.InvariantCulture)}",
365+
$"itemid={ItemID.ToString(CultureInfo.InvariantCulture)}");
368366
if (portalSettings.EnablePopUps)
369367
{
370368
editUrl = UrlUtils.PopUpUrl(editUrl, null, portalSettings, false, false);
@@ -391,11 +389,11 @@ public string GetProperty(string strPropertyName, string strFormat, CultureInfo
391389
}
392390

393391
//Retrieve the path to the imagefile
394-
if (strValue != "")
392+
if (!string.IsNullOrEmpty(strValue))
395393
{
396394
//Get path from filesystem only when the image comes from within DNN.
397395
// this is now legacy, from version 7.0.0, a real filename is saved in the DB
398-
if (ImageSource.StartsWith("FileID="))
396+
if (ImageSource != null && ImageSource.StartsWith("FileID="))
399397
{
400398

401399
var objFile = FileManager.Instance.GetFile(Convert.ToInt32(strValue.Substring(7)));
@@ -410,14 +408,24 @@ public string GetProperty(string strPropertyName, string strFormat, CultureInfo
410408
}
411409
else
412410
{
413-
if (!ImageSource.ToLowerInvariant().StartsWith("http"))
411+
if (ImageSource != null && !ImageSource.ToLowerInvariant().StartsWith("http"))
414412
{
415413
strValue = portalSettings.HomeDirectory + ImageSource;
416414
}
417415
}
418-
strValue = PropertyAccess.FormatString(strValue, strFormat);
416+
if (strValue != null)
417+
{
418+
strValue = PropertyAccess.FormatString(strValue, strFormat);
419+
}
420+
}
421+
if (strValue == null)
422+
{
423+
return "";
424+
}
425+
else
426+
{
427+
return strValue;
419428
}
420-
return strValue;
421429
case "vieworder":
422430
return (ViewOrder.ToString(outputFormat, formatProvider));
423431
case "createdbyuserid":

Components/Settings/Settings.cs

+1
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@
3636

3737
namespace DotNetNuke.Modules.Announcements.Components.Settings
3838
{
39+
[Serializable]
3940
public class Settings
4041
{
4142
#region constants

0 commit comments

Comments
 (0)