Forum: Core support ExiteCMS RSS Feed Generator v1.0 (Feed Manager) <![CDATA[ RE: Install Error . ]]> webmaster writes:
The installation page on the wiki states:
[quote]After installation, make sure the proper rights are set on this directory, and all files.

Obviously, the account your web server uses to run needs read access to all files and directories. Besides that, there are some directories the web server needs to write to.

These are:

* /files
This directory contains subdirectories for file and template caching, and for attachment (forum and personal message) storage.
* /images
This directory contains all images used by the different website modules.[/quote]

To me, that is quite clear? ]]>
Fri, 21 Jan 2011 11:10:26 +0000
<![CDATA[ Re: Install Error . ]]> alcomys writes:
sorry but there is no instrucion on witch directorys has to be writable.
or i need glasses.
i think there is lack of support on installing this exitecms core in detail. ]]>
Mon, 10 Jan 2011 10:51:55 +0000
<![CDATA[ RE: Install Error . ]]> WanWizard writes:
So I guess that the Apache user doesn't have write access to it.

The wiki page Installation72 specifies which directories (and all directories and files in those directories!) should be writeable by your apache user.

.htaccess defines access by users via a browser, and is not related to this message. ]]>
Tue, 02 Feb 2010 17:08:47 +0000
<![CDATA[ Install Error . ]]> kakun writes:
Please help .
Unable to run the ExiteCMS Setup:

[color=#NaNNaNNaN]The cache directory is not writeable.[/color]

Please consult the setup instructions on our support website on how to define the proper file rights.[/quote]

.htacces is ok configuration. ]]>
Mon, 01 Feb 2010 20:36:24 +0000
<![CDATA[ RE: Moderating ]]> WanWizard writes:
That feature that does not exist. You can move a message (or an entire thread) via de options of the moderator dropdown box, but both don't leave a placeholder. ]]>
Tue, 17 Nov 2009 12:16:31 +0000
<![CDATA[ RE: Moderating ]]> crisiswhatcrisis writes:
Another quick question on moderating: I can't seem to find how a moderator could remove a message in a forum, leaving a placeholder saying something like "This message has been removed as it did not conform with the board's rules on etiquette."

I'm again probably overlooking the obvious... ]]>
Mon, 16 Nov 2009 16:05:48 +0000
<![CDATA[ RE: align text in blog ]]> crisiswhatcrisis writes:
Yes, I'm on IE 8.
The funny thing is that it only does that in the Blogs, in the forums and articles it works as expected by default aligning left.

Anyway tnx for fixing it. ]]>
Wed, 11 Nov 2009 04:56:19 +0000
<![CDATA[ RE: align text in blog ]]> WanWizard writes:
Internet Explorer I assume?

It has a nasty habbit of inheriting parent styles when it is not supposed to. Firefox shows it as it should be. I hacked a quick fix, revision 2278. ]]>
Tue, 10 Nov 2009 22:05:28 +0000
<![CDATA[ align text in blog ]]> crisiswhatcrisis writes:
This should be a minor fix. A new blog's alignment is centered by default when published. Not very WYSIWYG. It surprises me every time again, and I have to go back in, select all text and click Align Left. ]]>
Tue, 10 Nov 2009 15:33:58 +0000
<![CDATA[ RE: n reads ]]> WanWizard writes:
Thats not easy to fix, as the "Read more" link is created at display time, in the page template, and not in de code. The code is not aware of what can and can't be displayed. ]]>
Sun, 01 Nov 2009 09:59:32 +0000
<![CDATA[ n reads ]]> crisiswhatcrisis writes:
I'm not sure whether this is a bug or a feature request.

If a news item or a blog is so short there is no "Read more" link, the "times read" counter does not get updated. ]]>
Sat, 31 Oct 2009 17:33:20 +0000
<![CDATA[ RE: Moderating ]]> crisiswhatcrisis writes:
Thanks for the explanation. Fair enough that this will be a feature request for the next major release. ]]>
Sat, 31 Oct 2009 17:20:09 +0000
<![CDATA[ RE: Last seen users ]]> crisiswhatcrisis writes:
Works for me! Tnx. ]]>
Sat, 31 Oct 2009 17:16:03 +0000
<![CDATA[ RE: Moderating ]]> WanWizard writes:
The administrative access a member has is determined by the rights assigned to that member via the User Administration, Administrators option.

You can also opt to assign these rights to a user group, which means that every member of the group will inherit the rights assigned to the group.

Every option (i.e. icon) in the CMS Administration section (Content Management, User Management, Website Administration) is a separate right that you can assign.

The only one exempt from this logic is the webmaster. A member that is assigned the webmaster privilege (User Administration, Administrators, select a user, check "assign webmaster privileges) has full access to everything. Default the only webmaster in the system is the account you created when you ran the setup procedure.

Most people have only one member that has the webmaster privilege, which is only used in emergencies, as most day to day tasks can be performed by members with specific administration rights to access those tasks. A member to which you have assigned ALL administrative rights is equivalent to the webmaster (in terms of rights, there are some differences).

Note that is principe is only true for administrative functions. Access to content modules like forums, blogs, albums, articles, etc is controlled by either assigning users the right to access, read, write, or use the module through the modules management interface. For example, you can assign both users and groups to a forum. Some modules don't have an administrative interface, but instead a group is automatically created when the module is installed, all you have to do to give access is to assign users to that group.

I know this isn't really consistent, but the difference between the two modes of operation has a long history...

To answer your last question:

If you want to delegate user and group management to other members, but you only trust them as far as you can see them, there is nothing you can do but do it yourself.

Anyone with group management access can create a group that has all administrative rights, and then assign himself to that group to elevate his rights. That's the way it works I'm afraid.

The way to solve that would be to have some kind of rights template that you can define, and which will be assigned to every new member. This would mean your untrusted moderators no longer need access to the user and group administration options, but only need access to the activation (and possibly blacklist) options.

This however isn't easy to implement, and given the fact that the current version is no longer under active development, we're probably going to add this to the list of features for version 8. ]]>
Thu, 29 Oct 2009 16:24:23 +0000
<![CDATA[ RE: Last seen users ]]> WanWizard writes:
That's a feature. smiley

Website Configuration, Main settings, field "Hide the status of the webmaster account?". ]]>
Thu, 29 Oct 2009 15:59:20 +0000
<![CDATA[ Last seen users ]]> crisiswhatcrisis writes:
I happened to notice that on my site my visits are not listed in the above panel.

But over here, I do see the webmaster's visit in the panel.

Is this a bug or a feature? ]]>
Thu, 29 Oct 2009 15:36:42 +0000
<![CDATA[ RE: Moderating ]]> crisiswhatcrisis writes:
I'm sorry but then I probably don't understand the concept of the security entity "administrator".

First I assumed that it was a member with moderator privileges, but you explained that forum moderators and bloggers are designated by making them member of a group with these privileges. If I understand correctly, administrators can do pretty much almost everything the webmaster can do.

What I am looking for here is a way to delegate membership applications and group membership changes to (some of the) moderators, without giving them the tools to assign to themselves the privileges equivalent to administrators or webmaster.

If this is presently impossible, I'll have to handle the member applications, activations, and group memberships myself. No big deal but I would prefer not to be indispensable in day-to-day operations. ]]>
Thu, 29 Oct 2009 15:25:12 +0000
<![CDATA[ RE: Moderating ]]> WanWizard writes:
Depends on what you mean by "administrator".

From an ExiteCMS point of view, an "administrator" is anyone that has, one way or another, access to at least one administrative module. That doesn't mean they automatically have access to all administrative functions.

To allow users to assign administrative rights, they need to be assigned the right to do so. This is a different right from user activation (which is a separate function that does just that). ]]>
Thu, 29 Oct 2009 13:16:14 +0000
<![CDATA[ RE: Blogging ]]> WanWizard writes:
Let me know if you do... smiley ]]>
Thu, 29 Oct 2009 13:10:55 +0000
<![CDATA[ Moderating ]]> crisiswhatcrisis writes:
I find myself in a catch-22 when attempting to define the authorization of the group 'moderators.'

I would like the moderators to be able to activate members, place them in groups, block/unblock them.
But it appears to me that they then could promote themself to administrator. (And kick me off the board smiley)

Surely someone must have come across this feature before me? ]]>
Thu, 29 Oct 2009 12:37:59 +0000
<![CDATA[ RE: Blogging ]]> crisiswhatcrisis writes:

Sorry, could not resist. Any other predefined groups missing? ]]>
Thu, 29 Oct 2009 12:33:41 +0000
<![CDATA[ RE: Blogging ]]> WanWizard writes:
Good question, I'll double check the installation procedure...

chips, next one on the road to intoxication is on me.

The groups were created as part of regular upgrades, but for new installations the setup didn't create them. Fixed in rev. 2274. ]]>
Wed, 28 Oct 2009 21:27:23 +0000
<![CDATA[ Re: Blogging ]]> crisiswhatcrisis writes:
Hmmmm, I honestly don't remember deleting any group....

Perhaps a mishap during installation?
Either that or I was too intoxicated to know what the heck I was doing... ]]>
Wed, 28 Oct 2009 07:21:08 +0000
<![CDATA[ RE: Bloggers ]]> WanWizard writes:
I don't see it show up? ]]>
Tue, 27 Oct 2009 18:49:04 +0000
<![CDATA[ RE: Blogging ]]> WanWizard writes:
Yup. Don't delete the blog groups! smiley

You shouldn't be able to delete system defined groups, so that's a bug I have to look into.


Hmmm... Can't reproduce that here. If I try to delete the Blog Editor group, I get the message "This group is either a built-in group, or belongs to a module. These groups can not be deleted", which is the correct response. ]]>
Tue, 27 Oct 2009 18:46:57 +0000
<![CDATA[ Bloggers ]]> crisiswhatcrisis writes:
I set "show in profile" and "show in forums" to No for the group Bloggers.

Yet it shows up in the forum. Bug or feature? ]]>
Sun, 25 Oct 2009 17:00:15 +0000
<![CDATA[ Blogging ]]> crisiswhatcrisis writes:

It seems I can't figure how to make blogs work. I have created a user group Bloggers with Bolg rights. Now where is the Blog Index maintained? I am probably overlooking something obvious... ]]>
Sun, 25 Oct 2009 15:41:37 +0000
<![CDATA[ More encoding issues ]]> webmaster writes:
Earlier today, one of our users reported an issue with database encoding, when they wanted to integrate a Trac website (like we do for our own Trac) with the ExiteCMS user database. (note: if you want to do that, we have a Trac 'egg' available to allow Trac to use the ExiteCMS user table for authentication)

They noticed that users that had an utf-8 encoded username (p.e. with chinese characters) couldn't login.

Upon closer examination, we realised that although ExiteCMS creates database tables in utf-8, and processes all data in utf-8, some PHP/MySQL installations have been configured to use other charactersets for the PHP-MySQL database connection, either through a setting in php.ini, or in my.cnf.

To fix this, we have altered the dbconnect() function to explicitly set the encoding of the database connection to utf-8.

Doing this will change the way PHP will interpret the encoding of the data retrieved, leaving you with funny characters on your website when it contained utf-8 encoded text.

To fix this issue, we created a new ISO8859-1 to UTF8 module, which will be visible in the webmasters toolbox. This version can convert the database online, by making two database connections, one with the old and one with the new encoding. Then it reads all data via the old connection, and sends updates out via the new one.

Still to do: Make it interactive, allow the webmaster to select a source encoding (now hardcoded to latin1), and ask for the webmaster password before starting the conversion, just as a failsafe.

Note that you have to make sure the encoding you select is correct, otherwise you will end up with corrupt data!!! As always, make a backup of your data before you start the conversion.

This module will be part of the upcomming v7.3 release. For those that can not wait, download and implement these changes:
- ]]>
Fri, 07 Aug 2009 23:20:48 +0000
<![CDATA[ Re: 7.2 Core Translation ]]> webmaster writes:
Welcome, and thank you for choosing ExiteCMS!

We're working on a module to add the translation process, but it is far from finished at the moment.

The easiest way to translate at the moment, is go to the /administration/tools directory, and copy to file "language_pack_English.php", to "language_pack_Balgariya.php". Open the file in your favorite editor, and translate the locale strings. They are sorted on module, so it should be quite strait forward.

We use versioning to prevent an older file from being installed. When you want to load your translations, look in the file for the define of LP_DATE, and increment the value by 1. This makes sure ExiteCMS sees it as an update.

To load your translated locale strings, go to the webmasters toolbox, where you now see your locale file, click on it, and choose upgrade.

If you want to share your translations, please post the translated file here, so we can include it in our next release. We'll make sure you recieve all the credits offcourse!! smiley

[quote]It looks like a fork of PHPFusion[/quote]
We forked from the PHP-Fusion v6 code in early 2006, but have progressed a lot since then. I'm pretty confident our version is better that their current v7 version... smiley

[quote]p.s. Also, Exite CMS seems not works on my host...[/quote]
ExiteCMS needs apache's mod_rewrite, and it looks like you haven't configured it. It is described in the wiki, page Installation72.

If you don't have access to the apache config, create an .htaccess file in the docroot of your ExiteCMS installation, and configure it there.

If you can't get that to work either, you're without a 404 error handler. You also have to change _header.tpl, which you can find in your theme directory, in templates/templates.

In the _header.tpl template, find all occurrences of "__0001", and remove those. So, the line which loads the CSS file should now read "exitecms.css". There's a javascript a few lines down that needs similar treatment.

Do this for all themes you have installed. ]]>
Thu, 15 Jan 2009 15:19:58 +0000
<![CDATA[ 7.2 Core Translation ]]> ep98 writes:
Can you point me to the right direction where is located each file in latest 7.2 distribution, I'm planing to translate Exite CMS to Bulgarian language.

It looks like a fork of PHPFusion, but at least support Unicode UTF-8 without any problems like the last version of Fusion 7.

Thanks in advance.

p.s. Also, Exite CMS seems not works on my host... is planed to be a demo and probably support site for upcoming users, when translation is done ]]>
Tue, 13 Jan 2009 08:12:47 +0000