Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Forum: Fixing WordPress
    In reply to: Domain Name Email

    Hello,

    Are you using services from https://wordpress.com or are you using a self-hosted WordPress installation from https://www.ads-software.com ? There are large differences between the two websites.

    If using https://wordpress.com then you can setup email forwarding, but there is no native email functionality. This means you can setup mail such as [email protected], and mail sent there will simply forward to say a Gmail account.

    Learn more here: https://en.support.wordpress.com/add-email/

    If you are self hosting with a provider such as Go Daddy, Bluehost, InMotion, etc, then you will need to contact your hosting provider for assistance with setting up emails.

    WordPress is CMS / blog software and does not provide features such as mailing inboxes. Those features are provided by hosting companies and mail solutions such as Google Apps For Business.

    In short if you want full featured email contact your hosting provider or enlist services such as Google Apps For Business. I advise consulting with a technical specialist if you are not sure how to handle setup.

    Hope you find this helpful!

    Forum: Fixing WordPress
    In reply to: Merge Users

    Hello,

    You can merge content from one user to another by deleting a user.

    1. Go into Users > All Users

    2. Find the account that you want to merge into another.

    3. Click “delete” for said user.

    4. You will then be brought to a screen with two options.

    A. “Delete all content”
    B. “Attribute all content to:”

    Choose option B. and all post created by the deleted user will be merged into the user you select.

    I advise creating a backup of your WordPress installation before proceeding in case you want to reverse the change later.

    Hope you found this helpful!

    Hello,

    There shouldn’t be any real drawbacks of using a custom php.ini file.

    By default your php configuration will typically adhere to the options set in the /usr/local/lib/php.ini file on the server (this can be different if your host uses technology like CageFS, but that is generally the file location in cPanel host)

    Using a custom php.ini file located in your users /home/user/public_html directory you are simply overwriting the default php configuration options with the ones you set.

    This gives you the ability to set the php configuration to match closer to your needs depending on the software you use. Say you need to upload large file sizes via php, but the host default value is low.

    You can change the post_max_size and upload_max_filesize values to anything you like to allow for larger uploads via php.

    To make the php.ini file work recursively upon all subdirectories add the following code to the top of your .htaccess file:

    SuPHP_ConfigPath /home/[CPANELUSERNAME]/public_html/

    If this code causes errors speak with your host as they may use another method.

    Hope you found this helpful!

    Hello,

    White screens of death will occur due to code errors. Even though the white screen may appear on the homepage, this does not mean the index.php file is the cause and you’ll want to make sure to look at other possibilities as well.

    Enable WordPress debugging and display error and see if any errors appear in the place of the white screen.

    Learn more here: https://codex.www.ads-software.com/Debugging_in_WordPress

    Try disabling all plugins and activating a default WordPress theme.

    If your hosting provider allows you access to SSH you can use the WP-CLI tools to manage plugins and themes. Using the WP-CLI tool you can sometimes be provided error messages that do not show themselves as easily by other means.

    Learn more here: https://wp-cli.org/

    Hope you find this helpful. If error notices show up after enabling debugging please let us know what they are!

    Hello,

    When it stops at 4% do any errors show up on the page? Anything like “HTTP Error”?

    Do you have access to error logs? Information on the issue may exist in web server or PHP logs. If you do not have access to web server logs contact your hosting provider and see if they can provide you information. They may also be willing to help turn on PHP logging if you are not sure how.

    Turn on debugging in WordPress as well: https://codex.www.ads-software.com/Debugging_in_WordPress

    Have you changed your hosting environment recently? Make sure the upload path is defined to the wp-content/uploads folder.

    Add the following code to the wp-config.php file and see if this helps: define(‘UPLOADS’, ‘wp-content/uploads

    More information on the upload path can be found here: https://premium.wpmudev.org/blog/change-default-wordpress-uploads-folder/

    If you find any error entries in log files please let us know what they are!

    Hello,

    Is your website built using another popular type of CMS software?

    You can find instructions on how to export existing content and import it into a WordPress application here: https://codex.www.ads-software.com/Importing_Content

    The link above offers instructions for several different applications.

    If you want to keep the same look and feel moving from one platform to another I suggest also consulting with a web designer / developer who can assist you with theme edits.

    Hope you find this information useful!

    Hello,

    I certainly recommend performing a backup before trying any of the suggestions made below.

    Replacing all the events calendar files with defaults from the developer will likely resolve this issue for you.

    You can find the default files here: https://downloads.www.ads-software.com/plugin/the-events-calendar.4.0.zip

    Rename the /home/content/17/10687117/html/wp-content/plugins/the-events-calendar/ directory to something like /home/content/17/10687117/html/wp-content/plugins/the-events-calendar.deactive/

    Then upload brand new files for events calendar.

    You can perform all of these actions via FTP or control panel interfaces. Hosting providers typically provide FTP and control panel guides in their knowledge bases.

    Hope this helps!

    Looking over the changelog provided in the link you gave I’m showing that Multisite support was added as of version 1.2.

    As long as you are using version 1.2 or above it will support multisite.

    Black pages are typically attributed to a error in coding.

    You can turn on PHP error logging and configure PHP errors to display on the screen rather than provide a blank page to help you narrow down the issue.

    Here is a guide from a hosting company that shows you how to enable such options: https://www.inmotionhosting.com/support/website/php-troubleshooting/troubleshoot-php-errors

    The guide provided is written for cPanel users, but the same information can apply to other servers as well. If the guide does not help you perform Google searches on PHP logging for your specific system type.

    When I visit https://amavqroo.mx/wp-admin/ I’m brought to a 403 error page.

    Upgrading will certainly help to resolve most any issue and should definitely be performed. There may be alternative troubleshooting steps you could take to get the website up and running in the meantime.

    403 errors have 3 most common causes

    1. Permissions issues. All files should the SuPHP friendly permissions of 644 and folders should be 755. This is true for any Linux based host. You can contact your hosting provider and request they perform a script to fix permissions.

    2. No index.php file. Check the directory of your WordPress installation and ensure that a index.php file exist. If it does not replace it with a default index.php file from the latest zip from https://www.ads-software.com/download/

    3. Errors or conflicts with code found in the .htaccess file. This is a file that makes changes to the web server configuration and effects the directory it is stored in and all sub directories. Rename the .htaccess file .htacess.deactive and create a new .htaccess file. Then add the following code:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    # END WordPress

    If you are not sure how to make the .htaccess changes yourself a supportive host may be able to assist you. This is typically out of scope for most web hosting companies, but you can always ask.

    Also you can replace directories like wp-admin and wp-includes with copies from https://www.ads-software.com/news/category/releases/
    I recommend renaming the current wp-admin and wp-includes directories before adding the default ones.

    Hope you have found this helpful! Thanks for reading!

Viewing 10 replies - 1 through 10 (of 10 total)