Mr Press

I managed to work this out. The link I found in a comment on your home page Tuxlog.

I also experience what I believe is a bug in the Weatherbug forecast. The date shown is one day later than it’s supposed. Instead of saying 3 november (tomorrow’s forecast) it says 4 november – but displays the forecast for tomorrow (which it of course should).

So to get the correct value i had to substract one full day on line 384 in func_bug.php:

$weather_arr['fc_obsdate_'.$i]= date_i18n($fc_date_format, $bt + ( $i * 3600 *24) - (3600 *24));

Now it works as it should.

I did some more testing.

What I found out is that also Facebook login and presumably all other social networks will generate a new user if the first user changed his email address in the profile page in wp admin area.

So it’s required to disable users from changing e-mail after auto registration, otherwise the existing user will not be recognised on the next login and a new user will be created. The same seems to be the case with the bio/description field value.

I don’t use the Theme my login plugin, but there may be a setting in the plugin to prevent users from editing email and bio. Otherwise those fields can be hidden by means of jquery and stop people from seeing them and thereby changing them.

When logging in with Twitter (including bouncer module) however, when the same e-mail address is entered, there’s an error notice that this e-mail address is already in use by another account. How will it ever be possible then (with or without bouncer) to link logins through Twitter to an existing account, like it is done with FB,LI,G+ etc.?

By not requiring users to enter e-mail manually on registration. I haven’t tested to require e-mail and I don’t see a need for it anyway. The registration works as it should without doing it. So I would advice you to disable the requirement for e-mail, delete the users again and try from the beginning and to prevent users from changing e-mail address or Bio description (About me). Name change works fine as far as I can tell. If this doesn’t work for you, try to uninstall all other plugins you are using one by one to make sure one of them is not the cause.

As for the bouncer I can’t tell, since I am not using it.

I haven’t tested it thoroughly, but there seems to be a workaround fix for this problem. Here is what I did:

1. Deleted all registered twitter users
2. Removed the following line from the file wsl.authentication.php located in wordpress-social-login/includes/services:

Remove or comment out line 841

'description' => $hybridauth_user_profile->description,

The social networks user descriptions will not be passed on to the new wordpress profiles, but that should be a relatively minor trade off for most.

Hope this works for you as well

I apologize for my late reply. Your callback for the quicktags indeed solves the problem. Many thanks!

I have the same issue with the quick tags not loading after a new comment is posted. I use the great and simple MarcTV Quicktags plugin which passes the admin area code editor quick tags to the comment form.

Great news. I would be very grateful if you could provide your code changes in detail or perhaps fork the plugin since I am doubtful it is still supported. Thanks!

Thank you for your reply and sorry for my late reply. I have managed to get the Ajax comments working with custom post types. I was trying to get the comments working by adding a rewrite endpoint, but could not. But I have skipped the endpoint for now, so it is not a problem. Thank you for the info on the callback. I will have a look at it and see if I can find a solution and come back here if need be. I also had a look at the no longer supported wp-comment-master which is not as finished as WP-Ajaxify-Comments but it works well since it doesn’t conflict with any of the aforementioned plugins.

The plugin has not worked properly for many months. It has been dropped from the repository without explanation. The support topics are still there.

To fix this comment out line 51 in the file gpp_init.php:

//'menu_icon' => ''.$plugin_url.'/img/icon.jpg',

Is this plugin discontinued?

Thanks David!

All-one-One Calendar has finally been removed after months of bother. It involved manually removing numerous options from the wp database. To remove the user roles and capabilities left behind by All-one-One Calendar install the plugin User Role Editor and delete them with the tools provided by the plugin. I apologize for my premature outburst, but I should also mention that this has been an unpleasant experience which caused a lot of extra work for our small business. The plugin is full of great features. If it had a clean uninstall all would be good.

This is not resolved by any means. The plugin was deleted from the dashboard. It leaves 500+ options in the database and it injects itself into cron tables. All the options left by All-in-One Event Calendar were manually deleted but after a while they are back in the database. This means that All-in-One Event Calendar has injected some code in the database which is very hard to detect and delete and which keeps re-injecting all the options once they have been removed.

If All-in-One Event calendar cannot provide clear instructions on how to delete this plugin entirely including all of the traces it leaves behind in the database our business may be forced to proceed to file a complaint against All-in-One Event calendar.

Please take responsibility for your product now and provide clear instructions on how to remove All-in-One Event Calendar completely!

Thanks Kevin. The form submission is now accepted (post creation). Great that you have changed the categories to a checklist. The selected categories, however, do not get appended to the post. All submitted posts become ‘uncategorized’ instead. The 0.2 add-on updates were successfully updated but when the plugin page was reloaded they were back to 0.1. Also, the success message is not shown. Maybe I got the settings wrong though or it is connected to the temporary lack of Ajax.

I get a blank white screen with the word “outside” written on it when trying to submit a post with the create post add-on. I don’t use Akismet or any other anti-spam plugin.