palatino

This issue has been resolved with version 1.0

I added this option. Now you may choose to display the individual display name, the username or the firstname.

Comes with version 1.0.2

With version 1.0 the issue with including the custom CSS should be resolved. The option to choose using custom CSS has been removed because just by adding the file and folder to your theme the file is included automatically.

Hi satori83,
I don’t think that is possible. But you might put the call <?php flexible_frontend_login_modal() ?> next to your menu call and style it the same way as your menu. The easiest way to keep your changes is adding a folder ‘flexible-frontend-login’ to your theme folder and drop the ffl-style.css file with your customizations in it.

Hi folks,
thank you for your patience and a special thank you to Boulli for the further development of FFL. I am working on updating the plugin with your ideas.

I see the problem. Next update will be compatible. Thanks for your patience. I will notify you when it is fixed.

Hi Li-An, thank you for your suggestion. I will put it on the list of future tasks for the plugin. Right now I am very busy so it might take some time until it is done.

Well, that is totaylly depending on your theme and the way the menu is called. What might work is to open the header.php or sidebar.php whereever the menu has been put.

The following is something which could work but probably needs some refinement and CSS styling. After the menu call in your file add
<ul class="same-class-as-menu"><li><?php flexible_frontend_login_modal() ?></li></ul>

You would have to make sure that on the options page you only activate the logout link for logged in users because otherwise you would end up with multiple links in the same menu item when users are logged in.

Good luck with it ??

Hi Deyson,

please check the plguin’s page. Click on the link “Click to log in” in the header (top right). Is that what you mean? If so it is already built in. If not please specify what you mean. I will be happy to add what you are asking for (if I know how to do it…)

Hi shortster,

you are right – that should be handled on the page itself. But since I am only a hobby coder it might be too difficult to implement because I do not know ajax processes very well which would be needed.

But I will think about it and find a solution adequate to my skills. I will let you know…

Hi Deyson,

redirect options are not available yet but that is definitely a feature worth implementing it.

I did not try this but there is a plugin called Peter’s Login Redirect and I could imagine it is a perfect fit for you. Please post here if the combination with Flexible Frontend Login works or not when you test it.

You might want to download the plugin once again since I have added a few lines which make the plugin working with Hierarchical Documentation without any hacking on your side. To your convenience ??

Yes I see, Hierarchical Documentation is using an older version of Markdown. I tried this solution and it worked in my test
install:

1. Copy the content of /flexible-frontend-login/includes/markdown.php to /hierarchical-documentation/app/libs/markdown.php
2. In line 7 of /flexible-frontend-login/includes/options-page.php change line 7 from this

   require_once( FFL_PATH . 'includes/markdown.php' ); // required to parse the readme.txt

   to this

   // require_once( FFL_PATH . 'includes/markdown.php' ); // required to parse the readme.txt
   require_once( ABSPATH . '/wp-content/plugins/hierarchical-documentation/app/libs/markdown.php');

Be aware that this is not a long term hack because any update of Flexible Frontend Login will erase those changes. I will include a check for the existence of Hierarchical Documentation in the next release but you should ask the developer to update the Markdown file in his plugin for better cooperation between the plugins.

Hi Bob,
as long as you use the “Hierarchichal Documentation” plugin you might want to use this workaround: Find the file /plugins/flexible-frontend-login/includes/options-page.php
Put // in front of line 7 so it looks like this:
// require_once( FFL_PATH . 'includes/markdown.php' ); // required to parse the readme.txt
It’s only a hack and you will have to renew it after a plugin update, but probably it will be the quickest fix.
I will keep looking for a more convenient solution but it may take some time.

Thank you for your notice. I added a fix and would love to hear if it helps. Please download version 0.97.4 and test it. Let me know if or if not that resolves the problem.