Forum Replies Created

Viewing 15 replies - 256 through 270 (of 927 total)
  • Forum: Developing with WordPress
    In reply to: Endif

    Hi, did you find the problem through the debugging hints?

    If your question has been answered, we would love if you would mark this topic as resolved in the sidebar. This helps our volunteers find the topics that still need attention and more people will get helped, possibly like you did.

    `wp_register_style(‘bootstrap’, get_template_directory_uri() . ‘/css/bootstrap.css’, array(), false, ‘all’);
    wp_enqueue_style(‘boostrap’);`

    If that was a copy and paste then you are missing a t in the wp_enqueue_style line. It should be:

    wp_enqueue_style('bootstrap');
    

    i.e. bootstrap not boostrap.

    That looks to be two separate bugs, but still bugs nonetheless. The JavaScript coding standards indicate that single quotes should be used (bug 1 being that you are being prompted to swap those with double quotes) and spaces should always be added inside parentheses (bug 2 being that you’re being prompted to remove them).

    I would suggest you file these two bugs individually with the simplest code example(s) you can create for reproduction of the issues at https://github.com/automattic/wp-prettier/issues.

    This sounds like it should be a ticket in the Core Trac filed against the “Site Health” component: https://core.trac.wordpress.org/newticket

    You will need to go restore a backup that you know is correct. Your WordPress files are all missing, returning a “404 Not Found” error when trying to access them directly. Seemingly the backup that was restored by your host was from after the files were deleted, or your files were immediately re-deleted once they had been restored.

    It is possible that your site has been hacked:

    Carefully follow this guide. When you’re done, you may want to implement some (if not all) of the recommended security measures and start backing up your site.

    First thing to try is to reinstall caldera forms, as the file that cannot be loaded is provided by that plugin. That is, you need to delete the plugin and upload a new copy from a known-good source. If that does not fix the problem, then the standard debugging steps apply:

    This may be a plugin or theme conflict. Please attempt to disable all plugins, and use one of the default (Twenty*) themes. If the problem goes away, enable them one by one to identify the source of your troubles.

    If you can install plugins, install “Health Check”: https://wordpress.org/plugins/health-check/ On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site.

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Hi,

    I just tried accessing your site, and it appears to be functioning correctly for me. Did you manage to resolve the issue?

    If your question has been answered, we would love if you would mark this topic as resolved in the sidebar. This helps our volunteers find the topics that still need attention and more people will get helped, possibly like you did.

    This may be a plugin or theme conflict. Please attempt to disable all plugins, and use one of the default (Twenty*) themes. If the problem goes away, enable them one by one to identify the source of your troubles.

    If you can install plugins, install “Health Check”: https://wordpress.org/plugins/health-check/ On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site.

    404 errors of this kind are handled by the server. You’re probably missing the .htaccess rules to point all requests to WordPress’ index.php file. This file can be recreated by going to wp-admin -> settings -> permalinks and clicking “save”.

    Alternatively you can try manually recreating with the default content below:

    # 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
    Plugin Author Dani Llewellyn

    (@diddledani)

    Hi,

    You haven’t specified a post-type so the default is used, which is page. Categories are normally not associated with the page post-type, so I think you likely want to tell the plugin that you want the post-type of post:

    [a-z-listing display="posts" post-type="post" taxonomy="category" terms="familycomputer"]
    
    Plugin Author Dani Llewellyn

    (@diddledani)

    Hi,

    I like this idea, but have no idea how to implement it at the moment πŸ™‚ I’ll need to read up on the available data that can be retrieved from a taxonomy to see how it might be done. I think it might require some rather ugly code (the best kind :-p)…

    Plugin Author Dani Llewellyn

    (@diddledani)

    Hi,

    To do this, currently, you need to add some custom CSS to override the in-built styles. The following is the CSS as shipped with the plugin, which will require changing the max-width of each entry, and the column-width in the first entry:

    .letter-section ul.columns {
        column-gap: 0.6em; /* the gutter size between columns */
        column-width: 15em;
    }
    .letter-section ul.columns.max-0-columns, .letter-section ul.columns.max-1-columns {
        max-width: 15.6em; } /* (1 x width) + gap - there is one gutter */
    .letter-section ul.columns.max-2-columns {
        max-width: 30.6em; } /* (2 x width) + gap - there is one gutter */
    .letter-section ul.columns.max-3-columns {
        max-width: 46.2em; } /* (3 x width) + (gap x 2) - there are two gutters */
    .letter-section ul.columns.max-4-columns {
        max-width: 61.8em; } /* (4 x width) + (gap x 3) - there are three gutters */
    .letter-section ul.columns.max-5-columns {
        max-width: 77.4em; } /* (5 x width) + (gap x 4) */
    .letter-section ul.columns.max-6-columns {
        max-width: 93em; } /* (6 x width) + (gap x 5) */
    .letter-section ul.columns.max-7-columns {
        max-width: 108.6em; } /* (7 x width) + (gap x 6) */
    .letter-section ul.columns.max-8-columns {
        max-width: 124.2em; } /* (8 x width) + (gap x 7) */
    .letter-section ul.columns.max-9-columns {
        max-width: 139.8em; } /* (9 x width) + (gap x 8) */
    .letter-section ul.columns.max-10-columns {
        max-width: 155.4em; } /* (10 x width) + (gap x 9) */
    .letter-section ul.columns.max-11-columns {
        max-width: 171em; } /* (11 x width) + (gap x 10) */
    .letter-section ul.columns.max-12-columns {
        max-width: 186.6em; } /* (12 x width) + (gap x 11) */
    .letter-section ul.columns.max-13-columns {
        max-width: 202.2em; } /* (13 x width) + (gap x 12) */
    .letter-section ul.columns.max-14-columns {
        max-width: 217.8em; } /* (14 x width) + (gap x 13) */
    .letter-section ul.columns.max-15-columns {
        max-width: 233.4em; } /* (15 x width) + (gap x 14) */

    You can add this CSS override using the Theme Customizer by navigating to wp-admin -> Appearance -> Customize

    Plugin Author Dani Llewellyn

    (@diddledani)

    Hi,

    It looks like you marked the thread as resolved. Did you manage to get it working correctly or are you still having an issue?

    Plugin Author Dani Llewellyn

    (@diddledani)

    Hi,

    You can add numbers in a single group at the beginning of the alphabet with the following shortcode:

    [a-z-listing display="posts" post-type="page" numbers="before" group-numbers="yes"]
    
Viewing 15 replies - 256 through 270 (of 927 total)