Repeater & Frozen Page

[globi]

Hallo!

I have a template which uses the repeater to handle simple blog-posts (instead of having the separate page for every single entry).
It was working just fine, but now the client notified me about the problem.

The page is editable, but only the posts before #108.
At post #108 the header-bar says: Blog Post #108 - Unpublished

I can't remove it, or do anything from the back-end...

Any clues?

Thanks!!

[Wanze]

Hi globi,

It's not a good idea to have your posts as repeater. Why? Scaling.

After a certain number of posts, you'll get problems with repeaters, because Pw has to load them all.

Maybe you're already facing this problem?

I'd suggest to write a script which loops through your repeater posts and add them as single pages.

Cheers

[globi]

BTW, when I count the number of repeater entries it says 107.

[globi]

Hallo Wanze, That really makes sense and I'm going to handle this problem that way.
Anyhow, I'd like to hear if someone know what could be the cause of this "Unpublished" issue?!

Thanks!!

[ryan]

What version of ProcessWire? you might try fixing it manually by locating the page through the page list tree via Admin > Pages > Repeaters > ...

[Arcturus]

I had this exact same issue. I had a page with 90 repeater records (the user went way beyond the specs they originally gave me) with #91 showing up as unpublished. Went to Admin > Repeaters as Ryan suggested and found 4 unpublished records. Deleting those didn't "unfreeze" the page. So I returned and manually deleted the last two populated records and was then able to make a title change to the page. I'm assuming that this some kind of memory-related issue?

[ryan]

Hard to say for sure. But those 4 unpublished records were most likely intentional 'ready' pages. This quantity is defined in your repeater field settings (details tab).