speedy222
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Access to ‘/!svn/me’ forbiddenAlso i get this info from the mail.
When using your svn, your ID – which is the same as your ww.wp.xz.cn login ID – is case sensitive. You cannot use SVN with your email address, only your user ID, so if your account is JohnDoe123HAY then yes, you need to use that exact ID.
Forum: Fixing WordPress
In reply to: Access to ‘/!svn/me’ forbiddenBefore i have the same problem and i type my username in low case iwebwebdesign that was not working and get the error !svn/me. But i ask it to support from WordPress. And he told me this:
That means you’re using the wrong username or password. Seriously.
iWebWebdesign is your username. Note the capital letters.
===
Afther this my login works.
That means you must the username and password both correct write with upercase and low case.
- This reply was modified 8 years, 2 months ago by speedy222.
Forum: Fixing WordPress
In reply to: Update to WP 4.7 is corrupting databaseOk i can not think wat the problem is. Maybe must you one role plugin install for admin roles or some file permissions to 777.
users must self register and create on profile.
Forum: Fixing WordPress
In reply to: Update to WP 4.7 is corrupting databaseOk have you not on error in the top than its ok.
Maybe you can try the new version from WordPress 4.8. You can download it here.
Go to you your FTP client and change the directorys and files in 4.8 version.
wp-admin
wp-includeschange files below in 4.8 version:
index.php
wp-activate.php
wp-blog-header.php
wp-comments-post.php
wp-commentsrss2.php
wp-cron.php
wp-links-opml.php
etc…NOT the wp-config.php
And NOT the wp-content directory thats your themes important is the wp-admin ans wp-includes and below files in the root.
Ather that login in your wordpress site than ask wordpress the database is change say yes ok change it and than it must good work.
Stay the problem than its maybe on plugin or theme problem.
Forum: Fixing WordPress
In reply to: Update to WP 4.7 is corrupting databaseI don’t no wat the problem is, but you can in your wp-config.php this text set to true.
define(‘WP_DEBUG’, false);/* That’s all, stop editing! Happy blogging. */
example: define(‘WP_DEBUG’, true);/* That’s all, stop editing! Happy blogging. */
maybe you find the error and you can make it.
meself i have not that problem.
Forum: Fixing WordPress
In reply to: Update to WP 4.7 is corrupting databaseok thanks for the 4.7 solution
- This reply was modified 9 years, 1 month ago by speedy222.
Forum: Fixing WordPress
In reply to: Update to WP 4.7 is corrupting databaseI have on solution for this that works. Download WordPress 4.5 and delete only the 2 directory’s with your FTP programma from your site:
wp-admin
wp-includesNOT THE: wp-content DELETE thats your template and upload images.
Than place the new directory’s wp-admin and wp-includes from the WordPress 4.5 in your site.
Login on your site: WordPress ask you upgrade the database. Say yes. And your database is now good working with 4.5.
open in the wp-admin directory the file update-core.php delete the php code and save the file. Now the upgrades from WordPress is stopped.
If you will new WordPress upgrades on your site, place on new file update-core.php in the wp-admin directory from your 4.5 download and the upgrades to 4.6 or 4.7 works if the error is maked from the 4.7 in the future.
thats the old code with the_avatar and need the user attachment. I have Classipress that is cp_get_image_url but that wil not working in the plugin file fep_class.php only give it no_thumb.jpg not the user image. We can help.
$threadOut .= "<tr><td><a href='".fep_action_url()."between&with=".fep_get_userdata( $post->from_user, 'user_login', 'id' )."'>" .fep_get_userdata( $post->from_user, 'display_name', 'id' ). "</a><br/><small><a href='".fep_action_url()."/author/, $to, 'display_name', 'viewmessage&id=$pID&order=$anti_order'>" .fep_format_date($post->send_date). "</a></small><br/>".get_avatar($post->from_user, 60)."</td>";Forum: Plugins
In reply to: [Front End PM] User disallowed to view message when admin interferes?For the database tables delete
only delete this database tables in your Mysql:
wp_fep_messages
wp_fep_metaYour user messages are also delete than.
afther that make the plugin front-end-pm install and active
And do not on update than it works normal
Forum: Plugins
In reply to: [Front End PM] "You do not have permission to view this message"For the database tables delete
only delete this database tables in your Mysql:
wp_fep_messages
wp_fep_metaYour user messages are also delete than.
afther that make the plugin front-end-pm install and active
And do not on update than it works normal
Forum: Plugins
In reply to: [Front End PM] User disallowed to view message when admin interferes?Sorry, it work not good with this option.
The anoher option can you do delete your database and deactive your plugin before and active your plugin. Do not make on update.
It works by my only your messages from every users are delete.
Forum: Plugins
In reply to: [Front End PM] "You do not have permission to view this message"Sorry, it work not good with this option.
The anoher option can you do delete your database and deactive your plugin before and active your plugin. Do not make on update.
It works by my only your messages from every users are delete.
Forum: Plugins
In reply to: [Front End PM] User disallowed to view message when admin interferes?Hello,
Go to your FTP client to your front-end-pm plugin.
click open the file fep-class.php
search this below code and delete it. Than you message is view on the site.
if ( !$pID )
return “<div id=’fep-error’>”.__(“You do not have permission to view this message!”, ‘fep’).”</div>”;Forum: Plugins
In reply to: [Front End PM] "You do not have permission to view this message"Hello,
Go to your FTP client to your front-end-pm plugin.
click open the file fep-class.php
search this below code and delete it. Than you message is view on the site.
if ( !$pID )
return “<div id=’fep-error’>”.__(“You do not have permission to view this message!”, ‘fep’).”</div>”;