Thread

Hi walpow,

I was able to login, and it looks like this PHP error was being produced (perhaps you weren’t logged in as a superadmin on the front-end, and weren’t seeing it?)

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30674 bytes) in ../mod.weblog.php on line 548

So, it looks like too many entries are simply being pulled. This would also explain the somewhat erratic behavior.

We think an easy fix would be to use the search= parameter in your weblog tag to check for an empty writer-blurb (instead of just hiding entries with the {if writer-blurb} conditional).

Give that a try and let us know how you fair.

Hey, Brandon -

I tried the search= parameter and got the same kind of erratic results. Spent an hour trying different combinations of parameters, with white screens showing up seemingly at random. Finally got the bright idea of logging on with the super admin ID I gave you, and the PHP error you mentioned showed up. So, yes, we’re on the right track with the memory thing, but it doesn’t look like the search parameter’s going to fix it.

Once we get that fixed, I’d sure like to know why the error’s showing up for one super admin (the one I gave you) and not another (mine, which I’ve been using successfully since I began the site).

Thanks,
Nathan

Hi Nathan,

I just had a look at the test template you’ve created and could generate any error, even without a limit parameter on the weblog:entries tag. This is with the search parameter that you are using. Have you perhaps changed or edited the way that the custom fields are setup?

It’s possible that you didn’t see the errors because your userside session did not contain the session ID in the URL, as specified at Admin > System Preferences > Security and Session Preferences.

Cheers

Greg

I just had a look at the test template you’ve created and could generate any error, even without a limit parameter on the weblog:entries tag. This is with the search parameter that you are using. Have you perhaps changed or edited the way that the custom fields are setup?

Yes, as it stands now it doesn’t generate an error. But I can’t get it to give the right results either. Ideally, I’d use search:writer-blurb=“not IS_EMPTY”, but that gives the error every time. So I tried to find some combination of words that would pull every entry I want (there are only six), and couldn’t do so without generating the error. Try, for instance, search:writer-blurb=“writes|master” and you’ll get the error. (The search:writer-blurb=“and” you see in the test template now was the last test I did before my last post.)

It’s possible that you didn’t see the errors because your userside session did not contain the session ID in the URL, as specified at Admin > System Preferences > Security and Session Preferences.

I’ve got that set to Session ID only.

Thanks,
Nathan

Hi Nathan,

With regards to the Session ID, even if you are logged into your control panel as a Super Admin and subsequently view a page on your website you will not be logged in with the same privileges unless your URLs contain ‘&S=’ and a long string of characters. You can make sure that this is case by using a front end member login template.

Cheers

Greg

Thanks, Greg. The front-end/back-end business is something that puzzled me when I first started working with EE, but I got it figured out a while ago and am indeed logging into the front end with my super admin ID. And I am getting the S with the long string of characters, but no ampersand before the S as you said. No ampersand with the super admin ID I gave you guys either, and that one is showing the error message.

walpow, where are you at with troubleshooting now?

We’ve established (I think) that I’m getting a PHP memory error with either method of selecting the entries to show - either using an if loop to run the code when there is something in the writer-blurb field, or preselecting the entries to be shown by using the search parameter on the weblog entries tag. I have tried all the suggestions you guys have presented; the memory error remains.

The secondary problem is why I can’t see the error when logged in through the front end with my own super admin ID. But since the one I gave you shows it, this can wait until later.

Hi Nathan,

Can you post the exact error you’re seeing on your end when using the search= parameter? I want to be sure we’re on the same page here.

Here you go:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 24782 bytes) in /www/eh12345678/public_html/fssys/modules/weblog/mod.weblog.php on line 548

walpow,

Lets just rule out any third party interference eating up your memory.
Can you goto your extensions and disable them using the large green button in the top right? Doing so will keep your settings intact. Do not disable individually.

Disabled the extensions, got same result. I have enabled them again.

walpow,

If you clear your cache via the CP and then refresh http://fourstory.org/writers/test. You will actually start to see entries appear. If you refresh the page after a few minutes they disappear. Bear with us while we look into this.

Thanks, John. I see exactly what you describe. I will await further developments.

Thanks for your patience, walpow. We’ll update this thread when we have any news.