Jump to content

esl

Members
  • Posts

    14
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Krasnodar region, Russia

esl's Achievements

Jr. Member

Jr. Member (3/6)

3

Reputation

  1. ProcessPageView::pageNotFound send 404 header, I can't send it once again. Problem solved using urlSegments on home page (plan B =).
  2. No, Adrian, I need to render a specific page on a non-existent address, with the address should not change.
  3. Hello! I'm trying to render a specific page (based on the URL) if the page is not found, using a hook in my module. But now I am faced with the fact that I can not use the "echo $p->render()" inside the hook because of incompatibilities with other modules (MarkupSEO). How and where do I hook "Page::render" to avoid rendering directly inside hook "ProcessPageView::pageNotFound". In short, I need to catch 404 error and instead of rendering error page - render another page with a status of 200, while using the hook "Page::render". public function init() { parent::init(); $this->addHookBefore('ProcessPageView::pageNotFound', $this, 'checkForceURLs'); } public function checkForceURLs($event) { $event->replace = true; // ... Defining $p - page i need to render echo $p->render(); return; }
  4. I think it would be a good solution to open the pages tree from the left menu on the panel (as in topnav), rather than a direct link to the home page.
  5. https://github.com/processwire/processwire/pull/54
  6. Yes, I have a similar situation. The user can upload the image size is not more than 2700x1800 (memory limit on server), but at the same time, he must use the images of at least 1920x330, as they are in this resolution will be presented on the site. And this error occures when I try to crop the uploaded image of size 1920x1280 to a minimum (1920x330).
  7. No, I have not tried yet. But I think if there is a bug in the core modules, it is necessary to fix in the first place, rather than relying on third-party modules. In any case, thank you.
  8. Yes, I also pay attention to it, but not well tested. Thank you for this. But I'm trying to crop the image to the minimum allowable values, it should not be a problem, I think. I'm loading an image that fits within the constraints. After all, it is a bug? As a workaround, we can remove the restrictions, but it is not an solution, I think.
  9. Export of field: { "header_image": { "id": 145, "type": "FieldtypeImage", "flags": 0, "name": "header_image", "label": "Изображение в шапке", "textformatters": [ "TextformatterEntities" ], "extensions": "gif jpg jpeg png", "maxFiles": 1, "outputFormat": 0, "defaultValuePage": "", "inputfieldClass": "InputfieldImage", "descriptionRows": 1, "gridMode": "list", "maxWidth": 2700, "maxReject": 1, "minWidth": 1920, "minHeight": 330, "fileSchema": 2, "collapsed": 0, "maxHeight": 1800, "outputString": "", "entityEncode": "", "useTags": "", "showIf": "", "columnWidth": 100, "required": "", "requiredIf": "", "unzip": "", "overwrite": "", "noLang": "", "dimensionsByAspectRatio": "" } } Try to import header_image field to reproduce error
  10. Yes, I checked, and all fields width name="width" is not required when I click "Apply". I checked other Image field, and it works fine with the same file.
  11. Hi, all! The problem is still relevant (tested on 3.0.40, 3.0.42 and 3.0.48) in Chrome browser only (tested on version 55) when trying to crop 1920x1280 to 1920x330. An invalid form control with name='width' is not focusable. ?id=1122&file=1122,dsc0828_obrez.jpg&rte=0&field=header_image&modal=1 Chrome can't focus hidden input with name="width" (which used for scaling, not for cropping).
  12. Thank you for your answer, Ryan. It would be nice to add opportunity of selecting 'PageAutocomplete' input field type along with 'PageAutocomplete*'...
  13. I apologize for my English (or GoogleTranslate's English ). Tried to search, but found nothing. Revealed the following problem: AutoComplete does not work if the page title contains Cyrillic characters. Checked by creating a page with English titles - they are displayed normally. Just tried in the advanced settings autocomplete select the "^=" mode. This leads to the fact that the list displays all the Cyrillic titles, regardless of the characters entered. Maybe I'm doing something wrong. Please help. -------- I found this: https://github.com/ryancramerdesign/ProcessWire/issues/129 It helps me. -------- One else question: can I use Autocomplete to select single page? What should i do? Thanks to all who participated in the development of this great CMS!
×
×
  • Create New...