nerdworker

Thanks so much!

This is probably a better way to code this:

echo __("Please log in !", "frontier-post")."?<a href=".wp_login_url()."?redirect_to=".get_permalink(get_option('frontier_post_page_id')).">".__("Login Page", "frontier-post")."</a>??";

One other quick suggestion would be to add a logout link or button at the bottom in case the admin bar is not displayed and to make it more obvious to log out when finished.

I only did a quick proof of concept and did not take the time to code it properly, but I went to frontier-post.php around line 102 in the code and added the redirect portion of the link. Something like this:

if ($frontier_show_login == "true" )
    echo __("Please log in !", "frontier-post")."&nbsp;<a href=".wp_login_url()."?redirect_to=http%3A%2F%2FEXAMPLE.COM%2Fmy-posts%2F&reauth=1>".__("Login Page", "frontier-post")."</a>&nbsp;&nbsp;";
else
    _e("Please log in !", "frontier-post");

Of course, this should not be hardcoded. The base URL and page that the frontier shortcode resides at should be done programmically, I just didn’t take the time to do this. But you can see the gist of it at least.

Please make the login link redirect back to the my-posts page after login. It’s dumping users into the backend, which will only cause confusion and defeat the purpose of using the frontend in the first place. I made the change locally, but would love to have it be permanent. Thanks! ??

Deactivate, delete, and reinstall seems to have corrected the problem. So far, no error messages and no emails from my hosting company.

I only ever installed and updated through the official WP plugin area, so not sure what happened. But at least it seems OK now.

Thank you for your prompt assistance.

I also receive this message, but have one additional thing to add:

Immediately after updating to version 1.7.3, I received an email from my hosting that indicated this:

Our systems performed a routine malware/virus scan on your account and unfortunately located infected/malicious files. We’ve automatically moved the infected files(s) out of your public_html directory into a safe, quarantined directory. Below is the file our scanners were able to locate:

[cut out path location]/ewww-image-optimizer.tmp/ewww-image-optimizer/optipng-linux ClamAV detected virus = [Heuristics.Broken.Executable]

My hosting thinks there is a virus in this file. Perhaps that is what happened in MPStranger’s case as well.

Is there a virus in this file? What should I do now?

In case this helps anyone else…

After investigation from my hosting provider, it turns out this is a Google receiving limits problem, as seen at this link:

https://support.google.com/a/answer/1366776?hl=en

ANOTHER UPDATE:

I think this was all because I created a category with a reserved term (‘year’). I was able to add my category back with a unique term and it appears to be working correctly now.

UPDATE:

It appears to have been caused by the custom taxonomy I added to one of my CPTs, but I have no idea why. I followed the instructions and it showed up fine. I did notice that even though I was able to add the categories to my CPTs, when I tried to list all posts associated with that Category, none would show up. So something was not working correctly anyway. But once I deleted that code, my custom permalinks are back to working properly. Very strange.

I have a feeling that I may be able to filter out the admin by using the wpseo_sitemap_exclude_author filter, but I’m not sure exactly how to use it. This filter is not listed on the Yoast site while covering filters for this plugin.

Would you please give me an example of how I would use this to filter out the admin? I know I would create a function in my functions.php file, I just need to know the specifics. Would I pass it the user ID? The username?

Thank you for any assistance.

This is still an issue in version 1.4.15.

I have manually corrected it in the class-sitemaps.php file by adding a check for the admin and excluding that user. However, I get tired of correcting this every time there’s an update.

As of update 1.4.15, this is still as issue for the Author titles. Rather than switch the lines of code as above, I’ve taken to simply eliminating the “!” in the line:

if ( !empty($title) )

becomes

if ( empty($title) )

solves the same thing but much simpler.

Please finally correct this issue.

Just another verification of this problem since the WordPress 3.6 update.

On first try, the Please Wait… button just hangs there.
On second push of the button, then the message “Invalid Data: Please go back and try again.”

Please update this plugin soon!

I would also like to see this. I would need the ability to email the post before I could consider this plugin.

I reverted back to the previous update (1.8) until this issue is corrected.