CARNET Web for Schools

In order for the school to use CARNET CMS system, it is necessary to activate it through the application for administration at http://admin.skole.hr.

In the menu on the left, you need to select “Web” and then “Web on Content Management System “.

Once the activation is complete, it is necessary to wait for a few minutes for the website to be visible at the school address.

After activation, other people authorized by the resource administrator may participate in the administration of the website of the school. See also: “Who can administer the school page?”

CMS activation process for schools at admin.skole.hr can only be initiated by the resource administrator (AR). It is recommended to use this role in contact with CARNET Support Services for CMS for Schools.

A registry administrator (AI) in a newly created school web in CMS may or may not have the same authority as the resource administrator.

In case there are more people who need to be able to edit school web in CMS, it is recommended to use the Group module to create a new group of authorized users in CMS. See also the question: “Can students edit part of the school page?”

In order to be able to administer, you must log in with the username and password assigned to the resource administrator.

If the resource administrator has no user data, directory administrator can assign them.

Due to the way in which HUSO system works, it is not possible to use a static and dynamic web at the same time at the same address www.nameoftheschools.skole.hr.

The module can be added after you log on to the school’s website as a resource administrator.

In the “Portal Management” menu, select “Edit Page” and click the down arrow in the column to which you want to add the module, and select a module that shall only be visible on that page or on all pages.

All students who are added to HUSO system and are synchronized within CMS of the school system can edit part of the site intended for the individual.

Exceptionally, if the resource administrator permits a student to administer the entire page by giving him privileges for administration, the student can edit the entire school page.

To delete the link from the navigation, you must select “Administration” in the “Portal Management” menu after logging in.

Inside the administration on the left, select the link you want to delete and delete it by clicking “Delete”.Once you have set navigation in the right way, choose “Save All Changes” from the right.

It is possible to set up your own CSS file and change the appearance/colour of the website. Detailed instructions can be found on this link. 

We must note that ‘CMS for schools’ is constantly being upgraded and optimized, so it is sometimes possible to apply the names of ID elements and their classes in the templates. In this case, if you are using your own CSS file, it is possible that something shall not look as originally conceived until your own CSS has been updated.

The layout and colour of school web pages created within CMS are determined by the template selected, so it is not possible to change colours except by choosing another template.

When the web in the content management system (CMS) is selected as a web type, the additional files cannot be uploaded to the FTP server, but the “Document Archive” module is used for this.

At the initial CMS-based web, all users who have been added to HUSO school system directory shall automatically be synced with the CMS.

When you add a user to HUSO directory later, synchronization can be done by selecting “Contacts from directory ” under “Portal Management” and then by clicking “Add new users”. Adding new users depends on the school year settings. 

• the first requirement is that there are students enrolled in HUSO directory for the new school year
• it is necessary to start the synchronization of the users with the directory (then the new information about the students are retrieved from HUSO system)
• only then shall the new school year appear in the drop-down menu

If the current year is not explicitly defined as ‘current’, the system shall automatically determine from the date which year is to be used, so that the “transition” to the next year shall occur 1.10.

The school may, if necessary, change the year earlier, and set up the next one to change timetables and grade lists earlier than scheduled (1.10).

Currently it is not possible to create your own modules. Modules from different CMS systems are not compatible and cannot be installed on CARNET CMS.

Since CARNET CMS installation runs automatically on the space provided for schools, its installation is not possible on other servers.

Below is a typical “troublesome” flash video that interferes the administration of the website and the way in which this behaviour of different flash objects can be regulated.

As you can see, the video covers the surface for editing Static HTML module. To avoid such a situation, click on the Flash icon (choose “f”) during adding the flash object, select “Properties” and select “Transparent” in the “Window Type” menu.

You can change the layout of the page regardless of the content. Regardless of the template change, all the content that you posted on the school’s website shall remain in place but released through the new selected visual.

One of the most common mistakes that occur when administering CARNET CMS is to seemingly delete a Homepage.

The same thing happens if you set a “Clean” layout that shall then display a clean white page on the Homepage.

Since it is CMS, the Homepage has not been destroyed and can still be managed if an administration link is accessed, which is in the form of: www.imeskole.skole.hr/admin/sites?asid=1

You need to set a layout that was previously selected and the Homepage will be redisplayed in the desired format. 

The users of CARNET CMS are solely responsible for the content posted on their school website, its installation and maintenance.

In the event of data loss, backup of the content is possible only in cases when data is lost:

• due to errors in the operation of CMS system that were not caused by the user,
• as a result of malicious security attacks on CMS.

In all other cases, restoring data backup is not possible.