kacsa

Hi,

The problem is not the value of the button, but the name field, which can be given to a PHP file.

Currently it looke like this:
<input type="button" value="Küldés" name="" style="" id="rm_next_form_page_button_2_1" onclick="gotonext_form_2_1()" class="btn">

As you can see, it has a value set, but the name field is empty. I need to give that field a value, in order to be able to send it to a PHP handler file.

Regards,
Kacsa

I might not understand what you want exactly, but can’t you just use a simple $_POST to get the info from the fields and store it in your database somewhere?

Ahh, thanks a ton, don’t know how I missed it.

Cheers

Hi,

I just arrived here, so sorry for the late reply. If it’s still a problem, here’s a solution:
This error occurs, when the user’s email can’t be requested for whatever reason (mostly because the user sets their FB email to not public). AFAIK the older versions of the plugin (like most other FB login plugins) used the email address to identify the user. Luckily it’s no longer the case here, so you can do the following:
Find the file class-facebook-login-public.php, it should be in wp-content\plugins\wp-facebook-login\public\ (you can edit it in WP as well). Find the line

if( empty( $fb_user[’email’] ) )
$this->ajax_response( array( ‘error’ => __(‘We need your email in order to continue. Please try loging again. ‘, ‘fbl’ ) ) );

and just comment it out. This way, the Email won’t be checked, so no error will occur.

Hope it helps.

Kacsa

• This reply was modified 7 years, 2 months ago by kacsa.

I already tried that, it only makes the sidebar go below the blog content.
Don’t worry about it, it’s not worth the effort.

Regards,
Kacsa

Hi,

Sorry for the late reply. Giving a link is not so easy, because it’s a site that is in development, plus I really don’t want to give out any info about the site itself, as it’s a somewhat secret project. Also, a lot of things have been changed, it has about a million plugins, half of them are customized, it has around 500 lines of extra css, so there’s way too much to configure.

Anyway, I checked around the codes and I really didn’t see any way to change the sidebar in that either (only the archives page, which I’m not sure if it’s the same).

I think I’ll just stick to the solution of using other sidebars on other pages, and just use the primary on the blog and change the widgets in that when I have to.

Regards,
Kacsa

I don’t think you’ll be able to do all that without adding a serious amount of extra CSS code. You can find the objects you want to change by right clicking on the object in the browser and selecting the last option (something like examine object?). Then you can add the extra CSS code in the theme options’ custom CSS tab.

Quick extra thing: I think your other site has a topbar set, that’s why the menu and logo are on a different place.

While, I’m at it:
If I’d try to modify the action-uv-registration.php file after the lines:

update_user_meta( $user_id, 'user_activation_key', $user_activation_key ); 
update_user_meta( $user_id, 'user_activation_status', 0 );

adding something like:

$conn = mysqli_connect("localhost", "user", "pass", "wp");
$result = mysqli_query($conn, "SELECT user_id FROM wp.wp_usermeta WHERE meta_value='$user_activation_key'");
if($result->num_rows > 1) {
$user_activation_key =  md5(uniqid('', true) );
update_user_meta( $user_id, 'user_activation_key', $user_activation_key );
}
mysqli_close($conn);

Would that generate a new key and update the value if it finds one already in that table? Or am I completely on the wrong track here?

If it’s a more complicated issue, then no worries, I’ll leave it as it is now.

Regards,
Kacsa

So, I failed to give up, cause I like this plugin so much.
If someone’s interested, I found a way to get it work, with a 99,99999999% success rate:
When an activation key is generated, it is stored in the usermeta table, where I can find the user’s ID based on the activation key meta value. I could then use the ID to link the two DBs.

I know that there’s a chance that two users can get the same key, but the probability of that is so low, I’m willing to take the risk ??

Regards,
Kacsa

Forgot to add, if I use login name manually, that works as well.

Thanks for the help, but I was able to get it done myself. All’s fine.

Well, nevermind, I thought I tried to add my code to the class_rm_frontend_form_reg.php as well, but turns out I didn’t and it works.

Thanks for the plugin anyway ??

Oh, forgot to mention: I guess the solution could be to put my code where I pick up the username and password to a different file, or different part of class_rm_public.php, because now I just threw it to the end of that file. I tried a couple of different spots, but the result was that my code didn’t work anymore.

Found a workaround, so this won’t be needed anymore.

Ok, I downloaded the latest translation, and updated a translation and now it seems to be working. Don’t know why it is as it is, but it sort of works now.