Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ItemManager 2.0
Hi Felix,

I think this is just a target value, it has default to a maximum of 200 px width, depending on the image size and orientation.

As far as I can remember UploadHandler uses these config values "thumbwidth" and "thumbheight" to resize images. You can retrieve them like this:
PHP Code:
$config imanager('config');
// ... 

Unfortunately, ItemManager 2 doesn't have an API to write the configuration directly, but that's not a problem since you can use default GS's SimpleXML method to overwrite it (not tested!):

PHP Code:
$config simplexml_load_file(IM_CONFIG_FILE);

// Whatever maximum value you want
$config->backend->thumbwidth 50;
$config->backend->thumbheight 50;

Note that the values would only apply to new uploads, the images that are already loaded will not be resized.
Hi Bigin,

I just uploaded my first theme: >>> ItemManager-Theme
After my first steps with the ItemManager v2.4.6 plugin I came up with a usable workflow
that seems practical enough to work with
- - - - - - - - - - - - - - - - - - - - - - - - - - - -

 ItemManager work flow to manage pages in a website

 1) Create a category: site-pages.
      In this category you create items that represent and hold the content for each website page.

 2) For each website page,  create an item such as: home-page,  about-page, contact-page, etc.

 3) You can also create an item for the sidebar.

 4) Create a category: gallery. In this category you create 2 items that represent the pictures and the script files.

      gallery item-1    gallery-pictures, for managing the pictures and each picture title or caption.
      gallery item-2    gallery-files, for managing the css and js scripts needed for the gallery to work.

 5) Create a category: album. In this category you create items that represent and hold the content
      for the pictures in each album.

 6) In the functions.php file create your functions and logic to output the content for the pages.
     Note that you can make use of both the GS api and the ItemManager api.

    The use of functions in your functions.php file has 3 advantages:

 a) it can wrap your output in any html you want for local layout and style (Generate markup)
      you can do this with the simple use of <?php echo "your html here"; ?>

 b) you can use both the GS api and the ItemManager api in the same function        

 c) it let's you easy separate logic from html layout in your page template files,
      in the template files layout all you need is <?php your-function(); ?>

 ItemManager automatically creates the folder structure where the content for each page (item) is stored.
 From the manager TAB in the GS backend you can manage all the categories, items, fields, etc.

Hello Felix,

yeah, this is an example of direct application. However, remember that the main purpose of ItemManager is to provide a basis for the development of user-friendly plugins and the direct application can be quite cumbersome.
Quote:... direct application can be quite cumbersome ...

I took it one step further and follow the amazing concept of the processwire cms/cmf where "everything is a page"
ItemManager allows to work with the same concept where "everything is a category"
Works great.
You got it, it's a similar concept or rather has certain parallels with it, yes

Users browsing this thread: 1 Guest(s)