Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter dlnovell

    (@dlnovell)

    Turns out I’m asleep at the wheel!!!

    Lesson learned: There’s an important difference between WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT

    Thanks for helping me work through it

    Thread Starter dlnovell

    (@dlnovell)

    I’ve just found a clue – when I changed the value in the default-constants.php file, it finally updated the value.

    Why would wordpress ignore the memory value set in 1) wp-config.php 2) php.ini and 3) .htaccess and rely on the default value?

    Thread Starter dlnovell

    (@dlnovell)

    I rebooted the server with no change.

    How can I determine exactly what configuration file this setting is being imported from? From what I understand, once a variable is set in WP it can’t be overridden by a later configuration file, hence why this setting needs to be higher in the wp-config.php file than the import. But, I’m doing that. Where else could it be coming from?

    Also, what’s the likelyhood that this has something to do with how Ubuntu 14.04/Apache 2.4 works (I’m fairly certain EC2 has nothing to do with it, it’s just an Ubuntu image, so any issues involved are Ubuntu related, as if I was running Ubuntu in a VM on my own machine)

    Thanks,
    Dave

    Thread Starter dlnovell

    (@dlnovell)

    There’s a chance I’m missing something, but on Ubuntu calling “services apache2 restart” is correct way to restart apache, correct? I did that after each change I made and it didn’t have any effect. I’ll try restarting the instance.

Viewing 4 replies - 1 through 4 (of 4 total)