ENews + Feedburner = &@%&#!

[Hawkeye]

Hi,

I've been using Feedburner with the ENews Extended plugin for a long time. Recently it seems to have broken and is no longer sending emails when I publish a new post.

In digging into the problem I have discovered that I originally added the Feedburner code to sidebar.php (years and years ago), and that's where the code still resides. However, I know that in Genesis proper I shouldn't be adding code to a Genesis file, so I'm wondering where exactly I should add my Feedburner code to be in compliance.

Does the Feedburner code belong in functions.php? Somewhere else?

Again, I am using the ENews Extended plugin, and when I click on the registration form I get the pop up from Feedburner which then registers my email for that service (which then doesn't work), but I want to make sure I'm doing all this correctly.

Thanks.

[Brad Dalton]

No need to add any code when using the eNews Extended plugin.

Just add your Feedburner I.D to the plugin settings.

Remove any code you have added to Genesis or reinstall genesis. Seems like you have hacked the Genesis files?

---

Tutorials for StudioPress Themes.

[Hawkeye]

Hi Brad,

If I hacked a Genesis file I did so long ago (years ago), when the original theme I was using necessitated such. I cannot find anywhere else that I inputted the Feedburner code, which would then be placing it in sidebar.php, so it really seems as if I must have hacked it, but by the same token the file date is recent, so I'm genuinely confused.

My version of Genesis is up to date, so I would think it would have overwritten any code I added, but the code is clearly there.

I've looked at every widget and setting I can think of and cannot figure out how that code is getting into sidebar.php, but I'll look again.

In any case, thanks for the note about not needing it. The very fact that I can see it means I don't have the ENews plugin configured accurately.

Update: Actually, I'm not sure if Genesis us up to date. In the Theme Settings it says this:

Version: 2.1.2 · Released: July 15, 2014

But when I look at the file dates of the actual Genesis files on my site they're from back in February, and probably older than that because I moved my ISP back then. So why wouldn't my Genesis files be updated when my admin panel says they are updated?

[Hawkeye]

Nope...wrong again. LOL

Current version of Genesis (all files 6/10/2015) shows in the Genesis folder on my site.

Sidebar.php in that folder does NOT show the code from Feedburner.

So back to the drawing board on all that.

And yet...Feedburner is still not sending emails which each new post. (RSS feeds works okay.)

!

Okay -- got it now. Here's why I was confused.

On my site I have the main WordPress directory, under which is WP-Content, Genesis and my Themes.

Genesis is up to date, my theme is up to date, and WordPress says it's also up to date, but when I look at the sidebar.php file in the WordPress folder, that's where I see the (old) Feedburner code. The sidebar.php file in my Genesis directory is as it should be, untouched.

So, how can I have an up-to-date install of WordPress that still shows file mods that I made years ago? And is Genesis overwriting those files or not? I would think it must be, but as you can see I'm easily baffled.

[Brad Dalton]

You should never modify WordPress files.

You'll need to find which files you modified or copy all the WordPress files as a backup and install the latest version.

Then you'll find out what doesn't work and have to fix it that way.

---

Tutorials for StudioPress Themes.

[Hawkeye]

Well, in my own defense we're talking about modifications that may be four or five or six years old.

I do understand that with Genesis none of that takes place, but if I remember correctly there was a time when modifying original files was necessary. (I have only modified functions.php for the past two or three years at least.)

In any case, it's curious that updating to the newest version of WordPress has never overwritten those files in the WordPress directory. In fact, I'm at a loss to explain how that might have transpired.

[Author]

Posts