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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesCoding PayPal Into DNN - Two Questions (IPN Handling & HTTPS)Coding PayPal Into DNN - Two Questions (IPN Handling & HTTPS)
Previous
 
Next
New Post
3/2/2011 11:32 AM
 
Hmm. Now I am confused: just use the https: etc. will use the ssl of the other party ? So instead of http you use https. Some payment providers do not accept a http request without using https (their certificate). If your site however does not use https on the call, the information is actually still not secured. I hope this clarifies your question.
J.
 
New Post
3/2/2011 4:32 PM
 
Store Integrator wrote:

1) Please check module development. I use WAP but you might use the default development module by which you place your code in the App_Code dir. You code goes either in a class in this directory or in the project for WAP. Once you compile the code is hit from your code to the code behind.
...

J.

 J,
    I am new enough at this that I am not able to figure out what "WAP" is or how I am doing it now (if it is WAP now).  I copied my IPN files(ppIPNi.aspx & ppIPNi.aspx.cs) to the dotnetnuke directory on localhost (C:\Inetpub\wwwroot\dotnetnuke).  The aspx contains one line:

<%@ Page language="C#" Inherits="QHWeb.Modules.Payments.View" AutoEventWireup="true"  Codebehind="ppIPNi.aspx.cs" %>

when I try to pull it up just to do the most basic test, i get:

Server Error in '/DotNetNuke' Application.

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: 'QHWeb.Modules.Payments.View' is not allowed here because it does not extend class 'System.Web.UI.Page'.

Source Error:

Line 1: <%@ Page language="C#" Inherits="QHWeb.Modules.Payments.View" AutoEventWireup="true" Codebehind="ppIPNi.aspx.cs" %> 

Source File: /dotnetnuke/PPIPNi.aspx    Line: 1


Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3618

Can you help me know I am suppose to know and tell me what I am suppose to do?
Paul

 
New Post
3/2/2011 4:59 PM
 

Hi,
I am not good at syntax. The best way to learn coding is looking at examples and on any error...Google..Google and see how others resolved it. I guess your syntax is not oke: <%@ Page language="C#" Inherits="QHWeb.Modules.Payments.View" AutoEventWireup="true"  Codebehind="ppIPNi.aspx.cs" %>

In DNN you only have .ascx files which are controls and not pages (aspx). Check out the Module template first and the developers guide of DNN and first generate an empty module and have it run. Then add your project to a new folder in DesktopModules and App_Code (or setup in WAP) and try to run that. Basically you can copy-paste your code in this module template which is used for setting up a new module....

This is my server code of Buckaroo:

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="BuckarooServerResponse.aspx.cs" Inherits="bBayt.DNN.Modules.ShoppingEngine.Checkout.Provider.PaymentMethod.Buckaroo.BuckarooServerResponse" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head id="Head1" runat="server">

<title>Server Response</title>

</head>

<body>

<form id="frmServerFeedback" runat="server">

<div>

<asp:Label ID="lblMessage" runat="server"></asp:Label>

</div>

<asp:PlaceHolder ID="plhInjectScriptInHtmlBody" runat="server"></asp:PlaceHolder>

</form>

</body>

</html>

This is inside DNN in the Desktopmodule folder:

<%@ Control Language="C#" AutoEventWireup="True" CodeBehind="SubmitView.ascx.cs"

Inherits="bBayt.DNN.Modules.ShoppingEngine.Checkout.Controls.UI.SubmitView" EnableViewState="false" %>

 
New Post
3/2/2011 5:25 PM
 
J, Three things. One, I was told to creat a NON-DNN module for my IPN Listener. So the one I created is non-DNN. I can create DNN moduels easy. Is yours DNN? I am not sure how to create a project as WAP. What in VS2008 classifies a WAP project? Two is the sample you gave your IPN listener? It does not look like one. That is what I am having issues with at this time. Three. I made the changes you spoke of, and the trace says it entered the module. Upon exit, I got: XML Parsing Error: no element found Location: http://localhost/dotnetnuke/PPIPNi.aspx Line Number 1, Column 1: I have not html on this page because an example I have for the IPN listener just have the page/codebehind line. Is this telling me I need a simple html form on this page?
 
New Post
3/2/2011 7:39 PM
 
Paul Johnson wrote:
J, Three things. One, I was told to creat a NON-DNN module for my IPN Listener. So the one I created is non-DNN. I can create DNN moduels easy. Is yours DNN? I am not sure how to create a project as WAP. What in VS2008 classifies a WAP project? Two is the sample you gave your IPN listener? It does not look like one. That is what I am having issues with at this time. Three. I made the changes you spoke of, and the trace says it entered the module. Upon exit, I got: XML Parsing Error: no element found Location: http://localhost/dotnetnuke/PPIPNi.aspx Line Number 1, Column 1: I have not html on this page because an example I have for the IPN listener just have the page/codebehind line. Is this telling me I need a simple html form on this page?

1. yes non-dnn is possible for the listener (the html page in an aspx page so that the codebehind does the logic). Our listener tells our server/ software the status of transactions even when the customer did close the browser or a transaction did not work out in a later stage. For that purpose we use the non-dnn. The dnn version we use to send the customer to the other gateway and to receive the customer back once the transaction is done or cancelled. or the customer has no money. In that case we want the customer to be back in the checkout page of dnn. Then the customer can see the final state and logoff. So we have both implemented: a dnn and a non-dnn. Both using https for going to the gateway and https to receive the answers back from the gateway and to have the customer in a ssl situation entering customer data like name, address etc.

2. A wap project can only be setup in a professional edition as far as I know. It is in fact that you create a project so that the compiler generates nice named dll's like MyCart.dll as set in the settings of the project. In App_code setup (I do not know how it is called, but it is the starter edition) then dlls are like aldfa9sf9saf393992.dll (kind of random key). The wap project gives you more control over the naming and when you want to compile stuff. In a large project you want to turn compilation off to speed up things. Disadvantage is that you cannot edit code during runtime. For both types of project setups it is vital your code is in the correct location. A dnn template for a first module will show you exactly the right places.

3. I answered your ssl/ https question and I am not good in syntax/ debugging stuff. I quite dislike. I normally have people around me to do the programming and I think of how all should look and work. If something is not working, best is to ask help. But at this point I cannot oversee what your exact problem is, where your code is etc. So I explain how we set things up.

4. We have an module with ascx file whith has a shopping cart and a checkout. These are dnn ascx controls inheriting from portalmodulebase.  If you checkout and want to pay, we create a remotepost (so that all querystrings are in the html body and encrypted instead of passing them in the url).  This remote post brings the payment details to the payment providers. The requests are https. Once the customer pays the answer is send back to our checkout page again (https call to our dnn page). if the user is not authenticated anymore, the payment info is shown, but nothing more (keep this also in mind that a user might log out). Meanwhile also a https request is done to our aspx page where the customer has no idea of. In some cases the server is faster than the client and visaversa. At that point we also run conversionscripts for affilates, google merchants, google conversion etc. That is what we do functionally and a bit technically.

You are basically in a technical issue which most likely is caused by a wrong module setup and not the code your are making. I would suggest first make an empty page (ascx) working without any code. Make sure the naming convensions are matching of the .ascx and the codebehing. No html is required on this page. Just put: TEST and it must be shown.

J.



 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesCoding PayPal Into DNN - Two Questions (IPN Handling & HTTPS)Coding PayPal Into DNN - Two Questions (IPN Handling & HTTPS)


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.