fesarlis

Sorry Lester, still does not work for me.

OK then.
So where can I ask any questions? Or you do not maintain the plugin anymore?

Thank you for the reply.

Unfortunately, this is just a security plugin. My problem is not how to hide wp-login.php. It is that Woocommerce REQUIRES wp-login.php to logout. This does not happen for login!!!

That discussion is really sad. All you managed is to make them even more aggresive about your work…most people will now hit their button and your plugin will be deactivated. This is clearly sabotaging your work, so I guess it is still your problem.

Φιλε μου μην ξεχνα? ειναι και το θεμα εθνικοτητα? στη μεση (Βαρ-Νται)…Ισω? η ομαδα του WordPress πρεπει να το λαβει αυτο υποψη. Ειμαι σιγουρο? οτι παιζει ρολο.

Anyone interested please feel free to translate the text above.

To put it more simply and in a realistic way. Yoast is necessary for many reasons that I’m certain you understand. In that sense, it would be better for your plugin if it coexisted smoothly with it. Unfortunately this is work that has to be done by you since they are not cooperative. Unless you are planning to convert your great work to a full-featured SEO plugin, in which case I personally would drop Yoast and switched to yours.

I am not familiar with the layout you refer to.

The Add-Meta-Tags settings are already divided into groups in the settings page. I try to keep the available options to the absolute minimum. This is a matter of principal for this plugin and is not going to change. However, further customization is possible to a great extent via filtering functions.

I just mean to create tabs and put the same options, and not use just one page.

The solution would be to assign the content (post/page) to the client’s account, directly from the post editing screen. If this setting is not visible, it can be enabled in the screen options.

Yes indeed. However this will be inefficient in sites where there are many people who add content. I don’t think it would be so difficult to move the settings you add to the profile page to your plugin’s options.

Thanks once again.

One more comment: It would be great if rel=publisher that links to Google+ profile page appeared everywhere.

Based on that and generally speaking, I think it would be much better if you followed a similar approach to Yoast’s settings. I mean, to divide options per social network (FB, Google+ etc) and give us the ability to enable what we want.

The current approach causes a simple problem.

I developed a website. Then gave the customer access to edit content. However, most of the content was uploaded by me (let’s call me ‘admin’).

In order for the social metadata to appear, I (admin) must set the website’s social pages as being MINE. In other words, I must set the customer’s FB page in admin’s profile page. This is not rational.

Thank you (Ευχαριστ? πατρ?δα).

All the info you provided is great. Yet it is not always clear what options constitute ‘similar features’. In that sense, it would be great if you told us exactly what features of your plugin could overlap with other SEO plugins. I guess that (unless you recommend all the common features to be deployed by your plugin :)) this would not violate any developer terms.

For example, let’s take schema.org markup. I (as a simple user) need more information to decide. What if your plugin sets microdata A and C, and Yoast’s sets microdata B and D? In that case I would want to enable both.

So (and since I really prefer to use your plugin) allow me to suggest a feature that can prove very useful.

You would add a page that just reads the site’s homepage and lists all metadata present. You could also provide the ability to disable ALL your metadata but NOT your plugin (not sure if you provide that already). In this way, we could see what metadata are set by the other plugins. Even better, you could do this automatically (list all metadata-others and yours) but not enable yours – to give us the chance to do it ourselves one by one.

Don’t know if I make any sense. Please let me know.

Yoast team seems to reject anything they did not create. It seems to me they consider themselves as the best of the best.

In my case, I use Woocommerce and have a custom product page. Yoast’s Opengraph did not produce the proper metadata. Disabled any relevant setting (now I use it only for title rewriting) and installed this great plugin. Now my metadata is perfect.

@george Notaras: Please let me know how to disable the article:author. All Woocomerce products have the site admin as author. Ability to customize it would be great.

No I don’t see anything else.

Also, nothing else changed.

Sorry can’t do that as this is an actively visited production site.

I have to note, though, that there was no problem with previous versions of nextgen. Don’t really know when the problem started, but there are directories that were created without changing the permissions. I kept updating the plugin, and suddenly the site admin complained that he cannot longer create directories. Had a look and found the above problem.

I understand. However, IMHO it would make sense if the issue was really resolved (as stated in the thread title). It is my understanding that the fix provided here was provided before the latest stable version (which I use), where the issue still remains. In other words, it looks that this thread should still be open and not marked as resolved.

I am not a programmer but I don’t see anything relevant in the changelog. I don’t really understand why you want a new thread for the same issue, but will do it.

Don’t know if it is the same issue. I use latest version 2.0.66.37. My galleries are located inside a directory ‘images’. I have noticed that setting this directory as 0775 is not enough. I also have to set the root directory of the site as 0775. You can realise that this is not acceptable and must be resolved immediately.

Use this (and put a & symbol before it).

#10004;