victorantos
2010-07-30T22:24:27Z
anyone successed to install 1.9.4 into a subdirectory?
MJCS
  •  MJCS
  • 64.4% (Friendly)
  • YAF Lover
2010-08-04T23:55:36Z
I was able to. You need to set the root and a few other things in the app.config. This is what worked for me:
<add key="YAF.Root" value="/YAF" />
<add key="YAF.BaseUrl" value="~/YAF" />
<add key="YAF.ProviderKeyType" value="System.Int32" />
<add key="YAF.UploadDir" value="~/YAF/upload/" />
billy10388
2010-08-06T07:18:54Z
Ganamede wrote:

Ok, I tried copying the contents of the 3.5 folder over and removed references to urlwriter.config. I'm still not able to compile.

I'll describe a little clearer what seems to be happening. Every control or element with a runat="server" and an id that is named in the .ascx control file is not being recognized in the .cs code behind. I tried opening a control and typing in my own server div tag like:
<div runat="server" id="testdiv"></div> but it was not recognized in the codebehind. I then put in the absolute path in the top directive for the CodeFile="~/forum/controls/xxx.ascx.cs" and then the controls for that page were recognized in the code file. I still get an error for it, but now its giving errors based on definitions and incorrect arguments instead of "does not exist in current context" like it did before I put the absolute path in.

I did some googling and found an article http://weblogs.sqlteam.c...ve/2009/02/21/60848.aspx .
It describes codebehind vs codefile which is exhibiting the same symptoms of my project.

Does any of this give anyone a suggestion as to what's going on? It appears as though there is a missing connection. I haven't even been able to get to the point where the settings and placement of my config files is even relevant.

Is there any other information or settings I can give that might help you diagnose the problem?

Thanks again.



Such a very amazing link!
Thanks you for the post.

_________________
Watch Step Up 3D Online Free 
Matija85
2010-08-07T14:37:52Z
Ok same problems here, what i did:

1- Move all "Forum/bin/*" to "bin/*", "Forum/App_Code" to "App_Code/*", "Forum/Images/*" to "Images/*" and web.config, app.config, mail.config, UrlRewriter.config, db.config from Forum to App Root.

then i edited app.confign adding:
<add key="YAF.FileRoot" value="~/YAF"/>
<add key="YAF.BaseUrlMask" value="http://www.mysite.com" />

If i got it right nothing else should be uncommented in the app.config?
Also in db.config should I change anything? If i got that file right it just says to my databse that it will create a user (forum) that will mess around the database later? Have i got it right? I already have a user on my database. could I just add the uid and pwd and somehow change connectionsstrign for db.config not to create a new user on the database but use an existing one and should that be changed in db.config?

As a web.config i used recommanded web.config that comes with the YAF, also i just removed the old web.config from root??

Thats all what i tried and when trying to install in by going to www.mysite.com  i get the error down.

Any sugestions? I am new to yaf and dnn but do my best to understand it :)

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

About Us

The YAF.NET is an open source .NET forum project. YAF.NET is supported by an team of international developers who are build community by building community software.

Powered by Resharper Donate with PayPal button

Project Twitter Updates

Copyright © YetAnotherForum.NET & Ingo Herbote. All rights reserved