No more create new page from page field after upgrade 2.6.13

[BFD Calendar]

Since upgrading from 2.6.1 dev to 2.6.13 I can't create new pages anymore from a page field.

Details Single Page or empty page, input PageAutocomplete and advanced *= and 'Allow new pages' checked.

I can type and see the list of pages appear, but when I type in a new name it just disappears when hitting return of clicking outside the field.

It worked fine before upgrading.

[Macrura]

Any chance the new pages are being created, but unpublished?

I had that same issue on '.12, and to fix it i think i had to reset the family settings;

[BFD Calendar]

Nope, they're not created.

[Macrura]

what happens if you re-create that same field as a copy on the same template - does it also not work?

Are there any errors in the console?

[BFD Calendar]

I have same type of page fields on other pages, they don't work either. On my 'places' page I have one for city input PageAutocomplete, one for state input PageAutocomplete and one four country input AsmSelect. Both PageAutocomplete don't add new pages while AsmSelect does.

Uhm, where do I put on console again?

[LostKobrakai]

You can see the console when opening the developer tools of your browser. This will tell you if there are any errors occurring from the javascript side. Also could you please do a Modules > Refresh in the backend? There where recent changes to make the autocomplete inputfield more compact for single select and it could be that you've still an outdated javascript file in the cache.

[BFD Calendar]

Refreshed modules several times, from different browsers. No errors in the console.

When I type or paste a new entry in the field the >> turns into a sad emoticon and then text entry disappears as soon as I click anywhere or save.

Checked in Firefox and Safari.

[bernhard]

you can use this module instead https://processwire.com/talk/topic/9857-module-page-field-edit-links/?p=100732

[Macrura]

@BFD Calendar - sounds like a possible bug; perhaps best course is to report it as an issue on github.

[BFD Calendar]

@BernhardB - Why would I need another module to do something which is just a basic feature of Processwire? My initial choice to use Processwire was because it's a simple easy to understand manage and use CMS. Including for people like me who aren't PHP wisecracks. As I said before, Processwire is to me a bit like an old Landrover, you can repair (almost) anything with metal wire, silicone and Rock'n'Roll tape. Just a regular lick of grease and gear oil should keep the machine spinning.

@Macrura - Thanks I'll report it there.

[bernhard]

sorry for suggesting...

[BFD Calendar]

Bernard, don't be sorry, suggestions are always welcomed. But I prefer simple solutions instead of making things more complex than they should be.

[SiNNuT]

Have you also cleared the browser cache of the browsers you are checking this with? Small chance but sometimes some old stuff sticks around (js/css).

[BFD Calendar]

Yep, tried that too.

[BFD Calendar]

The problem persists in PW dev 2.6.15.

[BFD Calendar]

And after another upgrade to PW dev 2.6.17 the problem still persists. Very annoying.

[BFD Calendar]

The Great Ryan solved the problem in PW dev 2.6.18. Hurray!