My problem is my code fails to send the Email and simply performs the CurrentUmbracoPage() method call.
To counteract this and find out what the issue is I have attempted to log the Exception that is generated using Log4Net however this does not appear to be working as nothing is written to the standard Umbraco log.
This is all occuring on a live server. I have published my development code using Visual Studio 2013 and then uploaded this published site to the server via FTP ensuring that the correct SMTP detals are entered into the Web.Config.
The one thing that concerns me and could be a cause of this issue is that this publish process seems to omit the /Controllers and /Models folders from my solution despite the actually being a part of the project. Is this an issue or are these compiled in .dlls?
To me it seems rather odd that the controllers folder is omitted and could potentially explain why the Email is not being sent..
Log4Net custom code failing to write to log
Hi all,
I have created a new Surface controller for use with my Umbraco 7.1.8 installation. My code is as follows:
My problem is my code fails to send the Email and simply performs the CurrentUmbracoPage() method call.
To counteract this and find out what the issue is I have attempted to log the Exception that is generated using Log4Net however this does not appear to be working as nothing is written to the standard Umbraco log.
This is all occuring on a live server. I have published my development code using Visual Studio 2013 and then uploaded this published site to the server via FTP ensuring that the correct SMTP detals are entered into the Web.Config.
The one thing that concerns me and could be a cause of this issue is that this publish process seems to omit the /Controllers and /Models folders from my solution despite the actually being a part of the project. Is this an issue or are these compiled in .dlls?
To me it seems rather odd that the controllers folder is omitted and could potentially explain why the Email is not being sent..
is working on a reply...