Christian Gatti
Forum Replies Created
-
Forum: Plugins
In reply to: [Separate Login] Import/Connect to external User DBHi Austin,
you need to keep at least one WordPress user in order to access to WordPress administration dashboard (back-end) because users registered or created through my plugin don’t have access to administration dashboard but only to restricted contents (front-end), viewable only by registered users and managed with plugin itself. In other words, you must keep the “normal” WordPress login method and you can’t use my plugin as the sole point of entry into the site.If you want to use my plugin as explained above (only on front-end side) and you need to validate users login by an external DB source, you have to edit code.
You should take a look to
separate-login/handle/seplog-manage-session.php
and modify$seplog_check_login_user
and$seplog_user_password_check
queries.Regards,
Christian- This reply was modified 7 years, 12 months ago by Christian Gatti.
- This reply was modified 7 years, 12 months ago by Christian Gatti.
Forum: Plugins
In reply to: [Separate Login] creating users?Thanks for using Separate Login Plugin!
You can create users from Separate Login admin panel (not WordPress admin panel), on frontend page. Log in with your Separate Login admin account, click on “Admin Panel” button and scroll down to the end of the statistic infos: you’ll find a section named “Create new user”. Fill in user infos and then press “Create” button.
That’s it!Regards,
Christian- This reply was modified 8 years, 1 month ago by Christian Gatti.
Forum: Plugins
In reply to: [Separate Login] Displaying Content to both Logged In and Not Logged InPlease, open this file with notepad:
/wp-content/plugins/separate-login/shortcuts/seplog-show.phpCopy and paste the code below at the end of the content of that file, just before the php closing tag (“?>”)
add_shortcode( 'seplog_show_to_everyone', 'seplog_show_to_everyone' ); function seplog_show_to_everyone( $atts, $content = null ){ echo '<div id="seplog-show-to-everyone">'.do_shortcode($content).'</div>'; }
The above function allows you to use a new shortcode:
[seplog_show_to_everyone]your content here[/seplog_show_to_everyone]
As you can easily imagine by the name of the new shortcode, the content inside is shown to everyone.
Bye,
Christian- This reply was modified 8 years, 1 month ago by Christian Gatti.
Forum: Plugins
In reply to: [Separate Login] Displaying Content to both Logged In and Not Logged InHi torquilcorkerton,
I don’t know why and how, but I missed out your request.. I’m really sorry!
For now I can tell you that I understand the issue, soon I will reply with a solution.
Bye,
ChristianForum: Plugins
In reply to: [Separate Login] [Shortcodes] in CF7Welcome back, Wolfgang.
This is definitely not a “Separate Login Plugin” issue, however you achieve the desidered result by “Contact Form 7 Dynamic Text Extension” plugin, as explained here.
Download it and install it, then create a contact form with CF7 by using “dynamic text” button and input the desired shortcode without square brackets (I mean that [seplog_show_email] turns into “seplog_show_email”).
Actually, the code for your need should be something like:
[dynamictext* dynamictextnam id:idname “seplog_show_email”]Regards,
ChristianForum: Plugins
In reply to: [Separate Login] Register without providing a usernameHi Wolfgang, thanks for your notes.
This plugin allows user to login through username or email (and, of course, password), therefore username has to be provided during registration process. Obviously this behaviour is a merely personal choice, not a mandatory process.
I agree that a registration option into widget should be present, so I’ll try to keep it in mind for a further release.
About wp_ prefix in table names, as far as I know, it isn’t required by plugin development rules, but it can be a good idea to use it.
Forum: Plugins
In reply to: [Separate Login] User Creation by AdminNew release is available for downloading or updating. It allows user creation from admin panel.
Enjoy!
Forum: Plugins
In reply to: [Separate Login] User Creation by AdminGlad to know that you like Separate Login Plugin!
The function that you are referring to, was not in the initial plan; however I can take it into account for the future updates, since it can be useful for many other users, as well as to you.
Stay tuned!
Forum: Reviews
In reply to: [Separate Login] Good ideaYes Ionel, users data are stored into “seplog_users” DB table.
Thank you very much for your gratifying rating!Tim, do not get mad..
I’ve solved by simply cleaning my browser (chrome) cache.
So sorry to having bothered you before performing this simple action.I take this opportunity to thank you so much for your wonderful (and moreover extremely useful) plugin, and also for your kind and polite support.
Bye,
ChristianTim, unfortunately I can’t increase memory limit, however, in my opinion, the log you’re referring to, is not directly attributable to the problem I described, because this issue came up after september 5th.
Don’t you rather think it could be something connected to Javascript? The problem basically involve the drag and drop option and drop-down menu function inside widget area. Moreover, if I set “Accessibility Mode” on widget page (under “Screen Options”) everything works flawlessly, because the page turns to static.
“Scan image files as if they were executable” it isn’t flagged.
Regards,
ChristianI didn’t say that I do not have access to log, I only said “no logs helping to find the issue”. Log only show something like this:
[05-Sep-2014 22:29:18 UTC] PHP Fatal error: Out of memory (allocated 36175872) (tried to allocate 786432 bytes) in /home/area101/public_html/wp-content/plugins/wordfence/lib/wfBrowscapCache.php on line 4100
However, notice that the above log concerns problems on previous dates.
If I do what you ask (“activate the plugin, try to access the parts of the theme you need to, and then deactivate the plugin”) no errors are shown.
My theme is PageLines Framework 2.4.5 (the same for working and not working websites)
Bye,
ChristianHi Tim,
thanks for your feedback.Here is the one from the “bad” website: https://www.nutfornuts.it/NOT_working_site.htm
Here is the one from the “good” website:
https://www.nutfornuts.it/working_site.htmAs you can see, both websites are hosted by the same server and almost all informations are common to each other.
Thanks again,
Christian