bishop335 / subtext

Automatically exported from code.google.com/p/subtext
0 stars 0 forks source link

Strange behaviours with multidomain blogs after upgrading to 2.5.120 #263

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I upgraded my weblogs from 2.1.0.5 to 2.5.1.20 and am having some 
strange behaviours. It may be due to my particular configuration not being 
tested much.

I have two domains and each has a virtual/application directory "/ 
weblog" that both point to the same physical directory that contains 
the subtext app. So that gives me two blogs on different URLs running from once 
application instance and one database.

My host is WebHost4Life. I also have local copies of them installed on 
my own test server. 

I'll refer to the domains as dA and dB. 

In the subtext_config table and HostAdmin, the domain is set 
appropriately and the application field/web folder is blank. I've 
configured a 404 custom error and created aliases for www.dA.com and 
www.dB.com. 

The weblogs are functioning but I have 4 problems: 

1) The URLs are not being constructed properly for dB but work fine 
for dA 
2) I get an unhandled exception logging in to Admin for dA but it 
works fine for dB (on WH4L, works ok local) 
3) BlogML export fails for both domains (bug submitted) 
4) In HostAdmin, the Title URLs for dB is actually for dA. However 
clicking on Edit shows the right details for dB. 

Further details for (1) and (2)

1) URL construction 

All links are being created in the form of XXX.com/XXX/weblog/... 

When I click on the link, it gets rewritten to XXX.com/weblog 

But this is only the case for dB and not dA. Their subtext_config 
fields are nearly identical and they use the same web.config so I'm 
baffled where the extra XXX could be coming from. 

In HostAdmin, the URL preview is fine. 

2) The file \App_Data\write.lock is causing an exception when I try to log into 
Admin under dA but Admin under dB works fine. The exception reports it is being 
used by another process. I can't delete the file.

Original issue reported on code.google.com by ian.wije...@gmail.com on 14 Sep 2010 at 9:53

GoogleCodeExporter commented 9 years ago
Regarding (1) above:

dB was pointed at hostdirectory/subdir and URLs were being constructed in the 
format of dB/subdir/weblog.

I have solved this by configuring dA and dB to point at the same hosting 
directory. This removed subdir from the path.

There's probably a bug in the way the path is parsed and URLs are constructed 
that doesn't take this kind of configuration in account.

Original comment by ian.wije...@gmail.com on 24 Sep 2010 at 11:36

GoogleCodeExporter commented 9 years ago
Not sure this is really a scenario we ever considered.
If you have two web application running pointing to the same physical folder 
then the lucene.net lock file will be accessed by two processes at the same 
time, and then you will have problems with the locking of the file.

The solution I suggest is that you have just one webapplication with 2 domains 
aliases on it. And then configure the 2 blogs to live under the domain/weblog 
folder.

Original comment by simone.chiaretta on 30 Nov 2010 at 9:28

GoogleCodeExporter commented 9 years ago
Do we have control over where the lock is created? Perhaps we could create an 
index per blog ID.

  /App_Data/1/...

And add a AppSetting to allow overriding even this.

Original comment by haac...@gmail.com on 30 Nov 2010 at 4:41

GoogleCodeExporter commented 9 years ago
Well... then in a multiblog engine we would have 1000 indexes :)
And we will have 1000 instances of the indexing and searching service loaded at 
the same time.
And we will loose the ability to do multi-blog search in the aggregator site.

Original comment by simone.chiaretta on 30 Nov 2010 at 4:44

GoogleCodeExporter commented 9 years ago
Ah, forget it then. Maybe an AppSetting for the "installation". That way, if 
you have 2 different web servers pointing to the same physical directory, each 
one can have its own index directory.

Thoughts?

Original comment by haac...@gmail.com on 30 Nov 2010 at 5:22

GoogleCodeExporter commented 9 years ago
Well... not only different web servers, also two different applications.
That could be done... But, still, I don't see the point in having 2 different 
websites pointing to the same folder: it accomplishes the same task of having 
one webapps and multiple domains on it.

Original comment by simone.chiaretta on 30 Nov 2010 at 5:53

GoogleCodeExporter commented 9 years ago
Yeah, I'm fine with not supporting that scenario.

Original comment by haac...@gmail.com on 30 Nov 2010 at 5:56

GoogleCodeExporter commented 9 years ago

Original comment by simone.chiaretta on 5 Dec 2010 at 3:19