|
|
 |
 |
Joined: 2/17/2012
Posts: 12
|
|
|
I'm receiving the following error message when I install the "My Account" module or navigate to the page the module is installed on:An error has occurred. DotNetNuke.Services.Exceptions.PageLoadException: The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>). ---> System.Web.HttpException: The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>). at System.Web.UI.ControlCollection.Add(Control child) at Smith.DNN.Modules.Registration.Current.ShowTrialVersion() at Smith.DNN.Modules.Registration.Current.Page_Load(Object sender, EventArgs e) at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---Just in case they are somehow related, this link shows the first issue you helped me get resolved: http://www.smith-consulting.com/Forums/forumid/5/threadid/11852/scope/posts.aspx This is my third day trying to get this module configured, all the functionality I need appears to be included in the module so I would really like to use it. Please Help!
|
|
|
|
 | |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hello,
Which version of Smith Reg Pro and DNN are you currently running?
With the MyAccounts module issue, have you set the Registration Page name in the MyAccounts module settings? Also, have you uploaded both the smithreglicense files to your server?
Regarding the jquery pop up issue, which page or pages is this issue present on?
Thanks,
|
|
|
|
| |
|
|
|
|
Joined: 2/17/2012
Posts: 12
|
|
|
DotNetNuke: Version 6.1.3 Community
Smith Registration Pro: Ver 4.34
The error occurs as soon as I add the module to a page or if I navigate to the page that the module is on so I'm unable to even access the module settings.
Both licenses have been added to the root folder.
------
The jquery issue is occuring on the page with the Registration module installed on it.
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hello,
I just tried to reproduce the same behavior I have not been able to replicate the issue you are reporting when adding the MyAccount module to a page but I have been unable to replicate the issue but I may not have the exact same configuration as you. Can you login to our test site and try to replicate the error. This will determine if the issue is with the latest version of the module or an issue with your specific dnn portal/module install.
Regarding the jquery issue if you open up the file of the page giving you trouble and comment out the following lines of code located at the top of the file, this issue should then be resolved:
<link href="http://ajax.googleapis.com/ajax/libs/..." rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/..."></script>
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/..."></script>
Thanks,
|
|
|
|
| |
|
|
|
 |
Joined: 2/23/2011
Posts: 6
|
|
|
Kevin, Posting my e-mail response here for reference in case anyone else ever experiences this issue:
------------------
Kevin,
I think I've narrowed the issue down a bit, we were able to install/add/configure the Register Pro "My Account" module on a local host DNN portal without any issues.
I tried several times to install /add/configure the "My Accounts" module on a fresh parent portal (version 6.1.3 Community Edition) hosted on our ResellerChoice account and received the same error every time (see attached files: My Account Module & Page Error.png & Event Log - My Account Module & Page Error.png). Each time I varied the process slightly to try and identify if the error is resulting from an entry in the settings or from the license and dll files that you sent to me to address the license issue but nothing stood out.
Aside from the "My Account" module issue, we are really liking the Register Pro module, the features included are spot on to what we need and I was able get it configured and run test transactions through our Authorize.net test account in less than an hour! We are also very happy with ResellerChoice who we have been with for over 3 years. They have good DNN knowledge and the service, support & response times are excellent.
We're anticipating additional Registration & Shopping cart deployments in the near to mid term so I'm really hoping we can figure this issue out, is there any chance of escalating it? I would be happy to coordinate communication with ResellerChoice support if that would help as I need to get this taken care of and soon.
In case there's a chance of this being an IIS related problem, I've attached screen captures of the IIS settings for the site (see attached file: IIS Settings.zip).
I really appreciate your help!
|
|
|
|
| |
|
|
|
|
Joined: 2/17/2012
Posts: 12
|
|
|
Kevin,
Please note the following in response to your e-mail suggesting we perform further validation of the Register Pro module:
-----------------------------------------
We have conducted a total of 18 controlled quality tests on the Registration Pro module versions 4.3.2 and 4.3.4 under the following conditions summarized below:
- DotNetNuke Version 5.6.1
- DotNetNuke Version 6.1.3
- SQL Server 2005
- SQL Server 2008
- In house development server / domain
- ResellerChoice hosting provider account
- Localhost test machine 1
- Localhost test machine 2
Results:
The My Account module in Version 4.32 installed without issue in every localhost test scenario
The My Account module in Version 4.32 installed without issue in every hosted test scenario
The My Account module in Version 4.32 installed without issue in every online dev server test scenario
The My Account module in Version 4.34 installed without issue in every localhost test scenario
The My Account module in Version 4.34 FAILED in every hosted test scenario
The My Account module in Version 4.34 FAILED in every online dev server test scenario performed
We identified two posts in the Smith Cart forums that may be related to a similar issue in the cart module. One of the posts appears to describe the exact same error message we are receiving and includes a reference to Smith.DNN.Modules.BuyNow.Cart.ShowTrialVersion(). In both instances it appear the issues with the module required a hot fix:
http://www.smith-consulting.com/Forums/forumid/1/postid/11289/scope/posts.aspx
http://www.smith-consulting.com/Forums/forumid/5/threadid/10965/scope/posts.aspx
Given the fact that version 4.3.2 of the module passe all test scenarios and that version 4.3.4 passed every localhost test and FAILED all host tests it would appear that this is an issue related to the Register Pro version 4.34, possibly with how it manages license notification in host based implementations.
We have logged 56 hours to issue resolution of Smith module we purchased on 2/17/2012 As I wrote in my previous e-mail we are impressed with the functionality offered by the Registration Pro module and would like to implement it on the current project and in future projects. I would greatly appreciate this issue being escalated as soon as possible.
Thank you.
|
|
|
|
| |
|
|
|
|
Joined: 2/17/2012
Posts: 12
|
|
|
Kevin,
We have made additional attempts to install the Registration Pro module on various hosted domains however are still unable to implement the "My Account" module in version 4.3.4 that we received due to the critical error that occurs when the module is added to a page.
We purchased the Registration Pro module due to the features described in your advertising materials and that we were able to implement with the Registration Pro version 4.3.2 trial module that we downloaded from your web site.
Thank you.
|
|
|
|
| |
|
|
|
Joined: 12/2/2011
Posts: 2
|
|
|
I too am having these exact same issues and do hope to use this product as it offers all the features we need in this build.
Best~
Juli
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hello,
I’m sorry to hear about the trouble you are having with the MyAccounts module, we have not been able to replicate this issue in a test environment so the issue must be getting caused by something unique with the your server/hosting setup or configuration. I have created a clean DNN installation, installed the module, uploaded the license and dlls you were provided then added the MyAccounts module to the page without any trouble.
Have you added the MyAccount module before uploading the dlls which you were sent to remove the licensing message?
Have you commented out the same javascript code on in the MyAccounts module which was causing the pop up issue when logging in?
Do you have any language packs installed on your portal?
It may be caused by an issue with your environment (hosting, server, iis, etc). Does your hosting provder, ResellerChoice, have any other clients using the Smith Reg Pro module? If the only difference between our testing environment and yours is the hosting provider, they may be preventing the module from functioning as it should.
Thanks,
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hi Juli,
Which version of the RegPro module and DNN are you currently running?
Who is your hosting provider?
Thanks,
|
|
|
|
| |
|
|
|
|
Joined: 2/17/2012
Posts: 12
|
|
|
Kevin, It appears this is not an isolated issue.
We have had several people involved in the effort to resolve the Registration Pro (MyAccount) module issue including two Microsoft Certified Developers with over 25 years combined experience (one is a former Microsoft employee) so I assure you we have used a very structured process and followed all steps you described.
Given that you are stating the MyAccount critical error is likely being caused by our hosting provider would you please provide the following:
- A list of hosting vendors that your module is known to work with
- Complete technical requirements for this module (asp.net framework version, permissions, etc...) so that ResellerChoice can troubleshoot this issue, which they have agreed to do.
- Any technical information that you are basing your opinion on that this is a host related issue
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
Hi Steven,
Can you login to our test site http://www16.smith-consulting.com/ and try to replicate the error. This will determine if the issue is with the latest version of the module or an issue with your specific DNN portal/module install. For login credentials, please send an email with a link to this post to kevin@smith-consulting.com.
Thanks,
|
|
|
|
| |
|
|
|
|
Joined: 2/17/2012
Posts: 12
|
|
|
We have been through this once already. The error occurs when the module is added to the page by the HOST. Your test environment is not a clean install DNN install and the test account is not a host account. This does not allow for a test case that comes close to that which the error is occurring in to be performed.
|
|
|
|
| |
|
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
The test environment is a fresh installation of DNN 6.1.3 created yesterday and we have installed the latest Registration module.
We have emailed you credentials to login to the portal, you will have Admin access so you can add, delete and configure all the settings.
This will determine is the issue is isolated to your environment or not.
Thanks,
|
|
|
|
| |
|
|
|
|
Joined: 2/17/2012
Posts: 12
|
|
|
Kevin,
If you are correct and this is in fact an issue caused by our hosting vendors environment I don't see how this would be helpful in resolving the issue.
As previously indicated, the version of the module that I received at the time of my purchase and fully tested prior to requesting my license key passed all test cases. If it is host related I'm curious why version 4.3.4 throws a critical error when the MyAccount module is added to a page but version 4.3.2 that I received at the time of purchase doesn't.
Assuming this is a hosting environment issue we are prepared to implement the site on an alternate provider. We have tested the both versions of the module on two hosting vendors and an internally hosted dev site, version 4.3.4 failed in each test case and version 4.3.2 passed each test case.
Rather than us randomly testing hosting vendors to identify one that the module will work with it would be helpful to us and I imagine other potential customers if you could provide the following information:
- A list of hosting vendors that your module is known to work with
- Complete technical requirements for this module (asp.net framework version, permissions, etc...). ResellerChoice has offered to troubleshoot our issue and has requested this information.
- Any technical information indicating this issue is host environment related that we can provide to vendors so they are able to verify their ability to support the module
I'm having two of our team members (a Lead Developer and a Quality Analyst) create and publish screen-cast videos of our test cases being executed again on several hosting providers.
The screen-cast will include the DNN site creation, module upload, installation, configuration, site event log, a complete folder & file listing for each test case site and detailed technical specifications for each host provider.
I look forwards to receiving the above information.
Thank you.
|
|
|
|