You are reading the Drake CMS Official Forums archive, available for historical purposes only.
Drake CMS has been rebranded into Lanius CMS, visit the new Lanius CMS Official Forums if you need support about Lanius CMS or Drake CMS -> Lanius CMS migration.
After upgrading and solving all my tarball problems, I have a new
one: I do not have any editor. The content is showed in html
coding with no editor attached to the backend.
I tried
to chang e the configuration to select tinyMCE as my editor and
got these error messages:
::/admin.php(83):
require(string[+43] =
"::/admin\components\config\admin.config.php") ::/admin\components\config\admin.config.php(100):
show_config(boolean =
true)W:\www\admin\components\config\admin.config.html.php(74): E8
Use of undefined constant _CONFIG_LDAP_AUTH - assumed
'_CONFIG_LDAP_AUTH'
I checked the config.php file with
notepad and it has tinyMCE listed as its editor, so what is the
problem? Help!!!!
legolas558
Re: Editor problems
03 January 2008 19:58
Anonymous
Report the full error dump in the bug tracker.
jolulipa
Re: Editor problems
03 January 2008 20:05
Anonymous
Sorry Legolas, couldn´t report the error. I´m having problems
with signing in sourceforge.
==Server== Drake CMS
v0.4.9 RC5 r5075 Server: Apache/2.0.59 (Win32) DAV/2
PHP/5.2.3 PHP version: 5.2.3 Protocol: HTTP/1.1 OS: Windows NT BNVINTRANET 5.1 build 2600 Database:
gladius Subsite: no
==Client== User agent:
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR
1.1.4322) Accept-charset: Accept-language: en-us User lang: do
=Debug backtrace= ::/admin.php(83): require(string[+43] =
"::/admin\components\config\admin.config.php") ::/admin\components\config\admin.config.php(100):
show_config(boolean =
true)W:\www\admin\components\config\admin.config.html.php(74): E8
Use of undefined constant _CONFIG_LDAP_AUTH - assumed
'_CONFIG_LDAP_AUTH'
legolas558
Re: Editor problems
03 January 2008 20:08
Anonymous
Yes, it's a bit tricky to use the trackers at SF.net...luckly
we'll soon have our bugzilla.
You are not using the
English language resources, fix your custom language resources...
jolulipa
Re: Editor problems
03 January 2008 20:19
Anonymous
Huh? Custom language resources?
Please be more
specific. In the back end I go to language manager and.... Or
is it something else?
thak you and regards,
trex1512
Re: Editor problems
03 January 2008 23:25
Anonymous
Hi
The default lang selection is found in the global
configuration dialogue under locale..
Good Luck
legolas558
Re: Editor problems
04 January 2008 01:43
Anonymous
Quote by jolulipa:
Huh?
Custom language resources?
Please be more specific.
In the back end I go to language manager and.... Or is it
something else?
thak you and regards,
You are using the "do" language files.
Dominican, I guess. Either disable it or fix it.
jolulipa
Re: Editor problems
04 January 2008 11:38
Anonymous
I moved the "do" files to other directory and copied
the "en" directory and cheged the name to do and I am
still getting the error message. I cannot modified the global
configuration dialogue because (remember) I cannot get into the
admin backend global configuration dialogue. the error i´m
getting is exactlly in that option. I could go a change the
config.php, but you have always recomend against it in favor of
using the dialogue.
Any ideas?
jolulipa
Re: Editor problems
04 January 2008 12:40
Anonymous
I think I now know where the problem is. I changed the default
edito to tinyMCE directly into a file ( it used to say midas),
for the sake of gaod I do not remember what file I changed.
Please tell me the file who has the default editor so I can
replace it and also tell me how do I go about changing (the
proper way) the default editor. In global configuration I do not
see any facilities to do that.
legolas558
Re: Editor problems
04 January 2008 14:29
Anonymous
Quote by jolulipa:
I
moved the "do" files to other directory and copied the
"en" directory and cheged the name to do and I am still
getting the error message.
This is not something that
you should do.
Please use the en
directory of the original installation and do not remove it.
Quote:
I cannot
modified the global configuration dialogue because (remember) I
cannot get into the admin backend global configuration dialogue.
the error i´m getting is exactlly in that option. I could go a
change the config.php, but you have always recomend against it in
favor of using the dialogue.
Any ideas?
Simple: you are getting these errors because you have
modified Drake CMS in a way that you should not, otherwise these
errors would not pop-up. The english language files should be in
the lang/ subdirectory. I suggest you to take them from the
version you are currently using (0.4.9?)
It is
impossible to have a Drake CMS of a certain version and language
files of another version. That's what happened to your
"do" language files. They were from an older version,
but you updated the CMS to a newer version. Hence language files
of an older version cannot work with a newer CMS, not before
being repaired and updated.
Is that clear now?
jolulipa
Re: Editor problems
04 January 2008 14:42
Anonymous
Crystal clear....
I did de the whole re installation
process and vrified the editor was working with de Drake sample
page, then modified my tarball backup to delete all .php files
and extracted it in the www folder. went into admin and
everything was working , even the editor. Then installed the new
templates package and choose a different template (Turquoise) and
then the editor problem came back... I could not see a editor
when editing content. So the problem is somewhere in the new
templates...
Any thoughts...
legolas558
Re: Editor problems
04 January 2008 15:34
Anonymous
Mmmh,
so when you use a default Drake CMS template you get no
errors?
And when using Tourquoise the editor is not
working?
Is this the situation?
jolulipa
Re: Editor problems
04 January 2008 15:53
Anonymous
Let me correct myself... The templates are ok. I installed the
CMS again and on top of it the templates package, and all are
working ok.
Is when I extract my tarball, that
everything goes bananas... I have deleted, almost everything from
the tarball, leaving only the private/drake, private/download and
media folders and still got the problem.
So the
problem is the tarball backup. Can you tell me what else can I
delete without lossing my site content?
Thank you
again legolas for your interest. This is very important for
me.
legolas558
Re: Editor problems
04 January 2008 16:05
Anonymous
Delete also the .php files inside the private directory.
Delete also the lang directory if present in the root.
What error do you receive? Always the same?
I am
glad to help you - you are having troubles because of a bug in
the tarball creation that now has been fixed.
If you
keep only the directories you mentioned, that should be OK.
I have another idea: are you using Gladius DB? Is the
private/drake directory containing the Gladius DB files?
In such case, remove the directory content (but not the
directory and the index.htm file inside it)
jolulipa
Re: Editor problems
04 January 2008 16:23
Anonymous
Yes.. I am using Gladius... Bud didn't get your solution.
Inside the \private\drake folder I have the Gladius Database
files all starting with de characters DK_ plus the index.htm adn
the gladius.db.master.php files. Tell me exactly which files I
can delete?
Regards,
legolas558
Re: Editor problems
04 January 2008 17:24
Anonymous
Quote by jolulipa:
Yes..
I am using Gladius... Bud didn't get your solution. Inside
the \private\drake folder I have the Gladius Database files all
starting with de characters DK_ plus the index.htm adn the
gladius.db.master.php files. Tell me exactly which files I can
delete?
Regards,
Open the
tarball archive and remove all php files from the private/drake
directory contained inside the archive.
Is the problem
fixed now?
jolulipa
Re: Editor problems
04 January 2008 18:17
Anonymous
The problem has been solved... Thank you again legolas for your
assistance and patience
legolas558
Re: Editor problems
04 January 2008 20:11
Anonymous
Quote by jolulipa:
The
problem has been solved... Thank you again legolas for your
assistance and patience
No problem, glad to see that you solved the
problem.
Editor problems 
Mmmh,
so when you use a default Drake CMS template you get no
errors?