webmarketingctm

@nameherocom Thank you so much! I followed your instruction, and because of it I found I actually DO have a php.ini file! I’m not very good with self-hosted servers at all and I thought the .htaccess and the php.ini files would have been in the same location. I found the memory code and adjusted it from 64 to 256, and my website works just fine! Thank you for your help!!

@t-p Thanks for your help too =) I’m not sure if I’m hosting on a remote server or not, as I really don’t know much about anything about this stuff ‘^_^ But I’m going to guess maybe not since I was able to fix the problem. Thank you both for your amazing help!

@t-p What does: “Please note, this setting may not work if your host does not allow for increasing the PHP memory limit–in that event, contact your host to increase the PHP memory limit. Also, note that many hosts set the PHP limit at 8MB.”

I have tried all of these things and I am still getting the fatal error.

@sterndata @otto42 My manager in the end was able to locate the root directory. I eventually found out that without knowing the URL of the webpage I was trying to visit, I couldn’t find any of the files. But in the end he remembered where it was.

Thank you for your replies! If you would tho, I just posted another question. I updated everything since it’d been years since the last time it was used, and now it’s giving me the fatal error for memory allocation. I’ve tried all the fixes and nothing seems to work… the web url is nelsongifts.com/ngifts – and the question title (in this forum) is called Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 72 bytes) in /home/nels1max/public_html/ngifts/wp-includes/class-wp-hook.php on line 286

In my case, the problem ended up being a DNS server issue. The domain was using our expired DNS servers when it should not have. Thus the domain was pointing to a shared i.p. address from a domain registrar. This caused Facebook’s share tool to deliver defunct URLs. So, in the end, it really wasn’t YOAST’s fault. Both the YOAST update I downloaded and the server issue just happened to happen at the same time.