Re: [AgentBristow] WYSIWYG editor question

Mon, 28 Apr 2008 11:44:59 -0700

Try adding the following into the stylesheet for your website:

p {
margin-top: 0;
margin-bottom: 0;
}

This will eliminate the linebreaks because of the

tags (although you will still see these linebreaks in WYSIWYG).

Jan

Re: [Dave] Notice: Roadmap & Feature Requests (post feature requests here)

Fri, 25 Apr 2008 11:23:29 -0700

Image library

It would be nice to have all uploaded images available in one library, in a way that it is possible to select images in the wysiwyg or upload fields form this library. Now you have to upload a picture each time if you want to use it in multiple sections.

Re: [InHouse] Discussion: Roadmap & Feature Requests (post feature requests here)

Fri, 18 Apr 2008 02:28:20 -0700

I know this is not the place to discuss this, but I just want to add a short comment on the discussion above because I think this is already possible in the current version: I use several checkboxes for this (for example "ShowinMenu", "ShowinArchive" etc.) and in the Listview I use the option "where ShowinMenu = 1" to select only those records I want to show in the menulist. The additional pages in the section that are not shown in the menulist can be accessed using the pagenum in a specific link.

Hopefully I understood the discussion correct and this is an option? So the developers can work on creating a new user role in version 1.14[;)]

Re: [Dave] Discussion: Roadmap & Feature Requests (post feature requests here)

Tue, 15 Apr 2008 13:57:07 -0700

I suggest to add a third role: "super user" which gives acces to all records but no access to the "admin only" fields...

See the discussion:

http://www.interactivetools.com/iforum/Products_C2/CMS_Builder_F35/User_Accounts_P61396/

Re: [Dave] User Accounts

Tue, 15 Apr 2008 13:55:29 -0700

The pulldown trick can be used for the menu item name, a nice trick!

But there are other fields as well, for example a checkbox to define wich pages (and titles) are shown in specific spaces of the menu and which pages can not be accessed using the menu.

In previous versions, I have used the admin only option for this and this was very helpfull. I suggest to add a third role: "super user" which gives acces to all records but no access to the "admin only" fields...

Re: [Dave] User Accounts

Tue, 15 Apr 2008 00:57:56 -0700

I have a section called "pages", with a field cald "menu name" and a field "content". The field "menu name" contains the menu item as shown in a list and I don't want the user to change this name. However, the user has to change the "content" field.

User Accounts

Mon, 14 Apr 2008 16:35:12 -0700

In version 1.12 it is possible to define different types of user accounts: Regular and Admin. Is there also something in between?

I would like to define User Accounts to have acces to ALL records, but who do not have access to the specific fields which are marked as "Admin only". Any options?

Thanks,

Jan

Re: [Dave] Upload results in fatal error

Wed, 26 Mar 2008 17:18:49 -0700

Hi Dave,

I didn't want to get into long complex calls with my provider (I'm satisfied with their support but it is not comparable with the support you guys provide me!). I have found some tips on:

http://www.ducea.com/2008/02/14/increase-php-memory-limit/

And I have added

[font "Courier New"]ini_set('memory_limit', '64M');[/#0000a0]

in "uploadForm_functions.php". That solved the problem.

My next questions are:

- in which other files should I add this line?
- can you advise me which value should be set (64M?)

The images I have tested were normal jpg's, with a maximum size of 3mb

Best regards,

Jan

Re: [jsv] Upload results in fatal error

Sat, 22 Mar 2008 06:28:16 -0700

The 'memory_limit' is 16M, that should not be the problem?

Is there anything else I can check and change to improve the upload proces?

Re: [Dave] Upload results in fatal error

Fri, 21 Mar 2008 18:12:44 -0700

Hi Dave,

If I turn off resizing, the images are uploaded without any errors.

After upgrading to version 1.12, and after turning on resizing again, I still receive errors:

Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 2816 bytes) in /home/wwwhulp.nl/public_html/cmsAdmin/lib/menus/default/uploadForm_functions.php on line 238

?

Jan

Upload results in fatal error

Fri, 21 Mar 2008 05:22:15 -0700

When uploading files with CMS, after a while I receive this error message:

"Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 2816 bytes) in /public_html/cmsAdmin/lib/menus/default/uploadForm_functions.php on line 230"

The picture size was 1,5 Mb. When uploading smaller pictures I don't receive errors. However, in CMS I have set the maximum size "unlimited" and within PHP the maximumupload size is set to 16M. Can you please advice me what to do?

Jan

Re: [Djulia] Format Date

Thu, 07 Feb 2008 16:50:35 -0800

Very helpfull indead, I have added the Dutch translations.

Re: [Dave] Weird charector in articles

Thu, 07 Feb 2008 13:06:57 -0800

It happened after saving, and each time I save the form again, extra Â characters are added to the ones already on screen.

It only happened when migrating content to the new CMSbuilder environment, so I do not expect this to happen (or bother me) again.

Jan

Re: [Dave] Weird charector in articles

Wed, 06 Feb 2008 18:15:19 -0800

Yes it hapened for example when copying (from a Word document):
-door Séphine

it appears in my wysiwyg as: SÂphine

Re: [Dave] Weird charector in articles

Wed, 06 Feb 2008 17:44:12 -0800

It could be, are they appearing in the wysiwyg editor when you paste them in, when you reload the article in the editor, or on the website?

If it's on the website adding a header might fix it. See this post: http://www.interactivetools.com/iforum/P59252#59252

Dave, what to do if it also appears in the wysiwyg editor?

Jan

Re: [Dave] Error in actionHandler.php on line 73?

Mon, 04 Feb 2008 16:22:16 -0800

Thanks Dave, that solved the problem![sly]

Best regards,
Jan

Error in actionHandler.php on line 73?

Mon, 04 Feb 2008 15:27:42 -0800

Hello there,

I realy like working with CMS! Unfortunately, all of a sudden (without making any changes) I receive this message after erasing records:

Notice: Use of undefined constant mysql_affected_rows - assumed 'mysql_affected_rows' in cmsAdmin/lib/menus/default/actionHandler.php on line 73

The records are erased, but the message is confusing ofcourse.

Can you explain me how to avoid this?

Thanks,
Jan