i’m unable to successfully delete a comment using the link generated by the {unwrap}{delete_link}{/unwrap}
tag which i’ve put in the “Admin Notification of Comments” Email Notifications Template.

the notification email includes a tag of this form:

http://mydomain.com/addons/ee/ee_system/?S=0&C=edit&M=del_comment_conf&weblog_id=4&entry_id=48&comment_id=23

which looks reasonable (the part up to “?” is correct), but when i click on it i am just redirected to my control panel. and when i navigate to the page with the comment in question, it’s still there.

im the superadmin, and im logged in at the time, although i assume this is supposed to work even if not logged in?

in any case, it’s not working… suggestions?

fogcity, just make sure you’re logged in using the www or non-www version of your site.

This link shouldn’t work if you aren’t logged in.

I’m logged in as superadmin on the non-www version of my site. The delete link still doesnt work.

I’ve also just tried logging in as superadmin on the www version of my site. No dice.

Also tried logging in as a registered user that has control panel entry delete privelidges. Again, no dice.

To reiterate, when I click the delete link appended to my comment notification email I am taken to the control panel home page (as a logged in user) but no confirmation message was issued and no delete has taken place. The link is of this form:

Hmmm.. I just did this on another of my sites, and I can’t replicate the problem you’re seeing.

Are you on the most recent build?

yes i am on the most recent build, 1.6.4.

1.6.4 is the version, 20080829 is the build number.

You can find that information at the bottom of any EE control panel page.

my Build number is 20080710

You are removing index.php, aren’t you? Try using

or removing the rewrite rule temporarily.

Ingmar, it looks like you are on the right track. The missing index.php is the problem. Good call.

The solution remains unclear, though… because the URL is generated by EE, in place of the {delete_link} tag. I am not composing the URL.

In that light, it seems like this is a bug… the system is generating a link that will not work, and ignoring the system setting that relates to whether index.php should appear in ALL urls it generates…

In any case, what do you recommend? I’m hoping this doesn’t require hacking EE system files.

fogcity:

Can you confirm that in:  CP Home ›  Admin ›  System Preferences ›  General Configuration

The URL to your Control Panel index page is in a similar format:  http://example.com/addons/ee/ee_system/index.php

Thank you,

-greg

Hi Greg,

My control panel index page is set as follows:

http://mydomain.com/addons/ee/ee_system/

I’ve removed index.php from that setting, as I would prefer to not have index.php in my urls.

Presumably, adding index.php back to that setting would make the system correctly generate the URL necessary.

But, the rest of EE works fine with it set the way it is…

This is the problem, please add index.php there again. This only affects the control panel, where it is needed as we have seen, and not the rest of your site.

that works.

a little bummed that index.php is in my URLs again, it looks messy.

(im sure some will think me silly for caring, however you will note that this forum has chosen to omit the index.php from its URLs)

Hi Greg,

I think the point was that as this isn’t going to be visible to anyone on the front end of your site, ie visitors and is only visible to admin members such as yourself and anyone else that has been made an admin then it isn’t quite as important visually to get rid of the index.php part?

fogcity - 03 September 2008 04:00 AM

(im sure some will think me silly for caring, however you will note that this forum has chosen to omit the index.php from its URLs)

That’s something that any non-logged-in or not admin member would see so in this case yes you are totally right that it may be preferable to get rid of them in this case.

And by the way, no you aren’t silly for wanting something like that at all

Best wishes,

Mark

fogcity, are we good? Or would you want me to move this thread to Howto? There might be a way to remove the index.php even from the control panel, for all I know.

i can live with index.php in the system path. it’s just not optimal.

as for the status of this thread, it still seems we have discovered a bug and thus it’s not best placed in how-to, especially if that would only result in suggestions on how to hack the system to work around it.

the delete-comment-link is being generated incorrectly by EE when the system path doesn’t contain “index.php”.

i haven’t found any other feature in EE that requires index.php to be in the system path, and regardless the fix seems simple: the code that generates the link should be made aware of the path setting.

i’m not mad about any of this, by the way, and i should mention i’ve been happy with tech support responsiveness.

fogcity - 03 September 2008 03:27 PM

it still seems we have discovered a bug…

I bet I know what the answer to that will be

I don’t think it is a bug as it isn’t supported to get rid of the index.php part in any shape or form in ExpressionEngine as this is a server related task which has nothing to do with ExpressionEngine. Don’t know if perhaps a .htaccess file could fix this one up though possibly?

fogcity - 03 September 2008 03:27 PM

it still seems we have discovered a bug

Actually, I don’t think this qualifies as a bug, since it’s working as intended.

the delete-comment-link is being generated incorrectly by EE when the system path doesn’t contain “index.php”.

It’s not generated incorrectly, it simply uses the path you provide. If you do remove index.php there, you’ll need to make sure that EE still finds the right page, much like you do when removing index.php from your public URL.