Quote:
Originally Posted by AndrewD
This isn't an error - it's a warning. When your server has a php configuration file that sets a value for <em>open_basedir</em>, this restricts the parts of the filesystem that *any* script can access. It is quite possible to set <em>open_basedir</em> and LDM's settings such as <em>file_root_prefix</em> to be incompatible, hence the warning.
|
I'm not overly experienced with the server side of things; but if we have had LDM running okay in the past, is this something that I need to worry about?
Quote:
The LDM code does not currently update its database records to change all the pointers for existing uploads and thumbs from the previous directory to the new directory. I can probably send you a straighforward bit of sql to use with, e.g., phpmyadmin, to make the update, and will add this problem to the 'to do' list.
|
No worries on sending the code. I just wanted to make sure that it wasn't a bug. Once we go live everything will be where it's suppose to be
Quote:
There are now (actually for some time in vb 3 also) two ways of accessing the comments system, one using the 'dropdown' method that you are probably used to, and the second using an extended 'inline' feature that you are observing. You can choose which you want on the admin/settings page. I think you've enabled them both to show simultaneously.
|
There we go! All fixed
Quote:
Probably, you ask so nicely 
|
Thank you
Quote:
This is a matter of caching certain bits of the display in order to gain speed. It is one of those things which gets tuned as one goes along, and was not a priority for this beta release. There is however a 'display bit caching' setting on the admin/settings page which is already partially functional.
|
I turned on the "bit_cache_active" and it did seem to load faster. Not sure if it's my imagination or not
I'll be doing more testing... we won't be going live until they get the CMS functioning better, but we are very excited about all the changes