I’m getting a blank page only on one page. I suspected a syntax error or memory (i up’d my mem to 128M btw).
I eliminated everything from the file until i was left with this:
{exp:weblog:entries weblog="payment_methods" dynamic="off" }
<div>
{payment_image}
</div>
<div>
<h2>{title}</h2>
{exp:textile}{payment_body}{/exp:textile}
</div>
{/exp:weblog:entries}
It still resulted in a blank page until i changed the payment_body field from textile to none. then wallah.. it worked. if i switch it back to textile it breaks again. so i figured maybe i have a weird bit of text in my field so i removed all the text in each entry and just put the word ‘test’… but textile still breaks the page…
any ideas?
this is just sooo weird.. i set up another weblog and field group that mirrored the first one and when i published entries it seems to work… I’m soooo confused…
{exp:weblog:entries weblog="testit" dynamic="off" }
<div>
{test_photo}
</div>
<div>
<h2>{title}</h2>
{exp:textile}{test_blurb}{/exp:textile}
</div>
{/exp:weblog:entries}
YIKES!!! now i’m getting really scared (i’m at the end of this 4 month project - it can’t go bad now!)!!!!
I created another weblog and used the same exact field group as the first one that failed.. then i was lucky enough to get an error only ONE TIME:
Warning: Typography::require_once(./system/plugins/pi..php) [typography.require-once]: failed to open stream: No such file or directory in /var/www/html/system/core/core.typography.php on line 470
Fatal error: Typography::require_once() [function.require]: Failed opening required './system/plugins/pi..php' (include_path='.:/php/includes:/usr/local/lib/php:/usr/local/php/lib/php') in /var/www/html/system/core/core.typography.php on line 470
And now i don’t get any errors… just a blank page…
Disabling them now won’t alter what’s already been done in the database. File was probably the culprit, see this thread for details.
If you use the same formatting type for all of your entries for the affected field(s), you can edit the field, change the formatting type, then edit again and change it back to the format type you want to use, and check the box at the bottom to update all existing data to use that formatting type. That will populate the column with the appropriate data for you.
When you used the File extension, any time you published an entry, that extension was not saving the field’s formatting to the database for that entry, instead leaving them empty. Now when EE goes to output that field, it doesn’t recognize the value (none isn’t a valid value) and so it tries to find a formatting plugin to match, hence the pi..php.
To fix this, all of those records need something inserted into the field formatting column for that field. You can do it manually in the database, or in the control panel, select the field, change the formatting type, save, change it back to what you really want, and check the box at the bottom to apply it to all existing content.
As far as what extension to use, I’m afraid I don’t have a recommendation beyond what’s been submitted to our add-on library, and I don’t believe an extension of that nature is there. You might email the author and see if they have updated the extension, or contact one of the people in the thread I linked to who experienced the same issue to see what their decision was on a final resolution.
To fix this, all of those records need something inserted into the field formatting column for that field. You can do it manually in the database, or in the control panel, select the field, change the formatting type, save, change it back to what you really want, and check the box at the bottom to apply it to all existing content.
derek, I’m looking in there now.. when you say all of “those” records what do you mean? Several field groups are using the File field type. do i have to do this to everything that uses the File field type? I’ve also been looking in my database and don’t know which table to look in to find an empty field.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.