esl

ProcessPageView::pageNotFound send 404 header, I can't send it once again. 

Problem solved using urlSegments on home page (plan B =).

Just now, adrian said:

Maybe I am not fully understanding, but it sounds like maybe you just want a $session->redirect($p->url).

Although be aware of redirecting 404's to valid pages in general - are you limiting this to certain pages for a specific reason?

No, Adrian, I need to render a specific page on a non-existent address, with the address should not change.

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;
}

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.

https://github.com/processwire/processwire/pull/54

25 minutes ago, SamC said:

Quick update. Removing the line:

$(".hide_when_crop").hide();

from ProcessPageEditImageSelect.min.js reveals a possible problem.

Thank you, SamC. I'll try.

16 minutes ago, SamC said:

@esl I think it's a bug too. Removing those values is not a solution for me neither. But I can't work out why it works at min-width 500 and not 1000.

I need users not to be able to crop less than 2400px wide (or upload images less than 2400px wide).

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).

13 minutes ago, adrian said:

Have you tried: http://modules.processwire.com/modules/croppable-image3/

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.

1 minute ago, SamC said:

@esl I believe these are causing your problems.

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.

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

15 hours ago, adrian said:

Have you checked the generated HTML to see what's going on?

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.

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).

Thank you for your answer, Ryan.

Note that the autocomplete is built as a multi-page input, so it may still behave as such on the admin side. 

It would be nice to add opportunity of selecting 'PageAutocomplete' input field type along with 'PageAutocomplete*'...