Updated: updated file hashes to share/filelist.md5. Upgrade check requirement.

Updated: Added missing method sqlite schema driver generateDropIndexSql (with another internal bugfix) which is required by the upgrade db check feature. Bugfix.

Merge pull request #65 from se7enxweb/display_size_and_item_limit

Display size and item limit

feat(admin): Add custom items-per-page input for content tables

Enhances content management with flexible pagination control:

User Benefits:
- Enter any custom number (1-10000) for items per page display
- No longer limited to preset values (10, 25, 50, 100, 200, 500)
- Ideal for bulk operations requiring specific item counts
- Keyboard-friendly: Enter key applies value immediately
- Auto-validation prevents invalid inputs with clear error messages
- Works seamlessly with existing pagination and table options

Use Cases:
- Content editors managing large folders can set exact display counts
- Batch operations become more efficient with custom page sizes
- Performance testing with specific item counts
- Export/import workflows requiring precise item ranges

Technical Implementation:
- Added custom input field with radio button in table options panel
- Input validation: positive integers only, 1-10000 range
- Enter key and blur event handlers for flexible input methods
- Integrated with YUI DataTable paginator API
- Clean error handling with user-friendly alerts
- Consistent styling with existing table options UI

Files Modified:
- ezajaxsubitems_datatable.js: Custom input handler and event listeners
- yui_container.css: Flex layout styling for custom input field
- children_detailed.tpl: Added translation label for 'Custom' text

feat(admin3): Add customizable left sidebar width and font sizing

Implements comprehensive left sidebar customization for improved user experience:

User Benefits:
- Choose from three preset sizes (Small/Medium/Large) for quick adjustment
- Drag-to-resize functionality for pixel-perfect custom widths
- Font sizes scale automatically with sidebar width for better readability
- Preferences persist across sessions for consistent workspace layout
- Improves accessibility for users who need larger text
- Optimizes screen space for users with different monitor sizes

Technical Implementation:
- CSS variables (--left-sidebar-width, --left-sidebar-font-size) for dynamic sizing
- Pointer events API for smooth drag-resize with capture support
- CSRF-protected AJAX preference saving via ezformtoken
- Three preset sizes: Small (16rem/13.16px), Medium (22rem/16px), Large (30rem/20.88px)
- Custom widths saved as pixel values with 224px-72vw range
- Font inheritance ensures consistent sizing across all menu elements

Files Modified:
- ezadmin_menubar.js: leftMenuResize() and leftMenuWidthControls() functions
- pagelayout.css: CSS variables, font sizing, resize handle styles
- pagelayout.tpl: Server-side CSS variable injection based on user preference
- page_leftmenu.tpl: Added resize handle element

Merge pull request #64 from se7enxweb/admin3_more_actions_hide_unhide_controls

Add hide/unhide controls to admin3 subitems More actions menu

Add hide/unhide controls to admin3 subitems More actions menu

## User-Facing Benefits

**For Editors & Content Managers:**
- Two new bulk actions in the admin3 subitems 'More actions' menu: 'Hide selected' and 'Unhide selected'
- Editors can now quickly hide/unhide multiple nodes from the subitems list without navigating away
- Consistent workflow with other bulk operations (delete, move, etc.)
- Reduces clicks needed to manage node visibility in large content trees

**For Site Admins:**
- Visibility state changes flow through the standard eZ Publish operation system with proper permission checks
- Node state changes are recorded through the normal content change tracking layer
- No new database tables or special infrastructure required

## Developer & Maintainer Benefits

**Implementation Quality:**
- Uses existing eZContentOperationCollection::changeHideStatus() handler
- Integrates cleanly with the legacy content/action module dispatcher
- Both kernel base implementation and extension override (nxc_powercontent) support the feature
- Minimal new code surface area reduces maintenance burden

**Testing & Confidence:**
- New PHPUnit regression test (eZContentActionHideUnhideRegression) verifies:
  - Hide action correctly changes node state and redirects
  - Unhide action correctly changes node state and redirects
  - Real module dispatch path is exercised end-to-end
  - POST payload handling is validated
- Test is part of the kernel content suite and runs with every build
- BC documentation at doc/bc/6.0/ explains alignment points for future changes

**For New Contributors:**
- Clear entry point: see admin3 template wiring in design/admin/templates/children_detailed.tpl
- Backend integration is a reference implementation of bulk action dispatch
- Regression test serves as a working example of module/action testing pattern

## Technical Changes

1. **UI Layer** (design/admin/):
   - Added Hide selected / Unhide selected buttons to children_detailed.tpl
   - Updated yui_menu.css for consistent styling of new controls
   - Enhanced ezajaxsubitems_datatable.js to wire button submissions

2. **Backend Handler** (extension/nxc_powercontent/modules/content/action.php):
   - Added HideButton/UnhideButton post variable detection
   - Processes SelectedIDArray node IDs
   - Checks can_hide permission per node
   - Calls changeHideStatus via operation handler or direct collection method
   - Redirects back to parent view after operation

3. **Regression Coverage** (tests/tests/kernel/content/):
   - New test class eZContentActionHideUnhideRegression in ezcontentaction_hide_unhide_regression.php
   - Wired into kernel content test suite (suite.php line 20)
   - Verifies both hide and unhide paths with real node objects

## Backward Compatibility

- No breaking changes to existing module interfaces or data structures
- New menu items are non-breaking UI expansions
- Kernel action.php implementation provides compatibility layer if extension is disabled
- Existing hide/unhide workflows (via edit forms, direct API) remain unchanged