Forum Replies Created

Viewing 15 replies - 721 through 735 (of 3,259 total)
  • Pls look in Dashboard > Appearance > Widgets
    Maybe something with “meta”

    Sorry to be pedantic, but the issue is to go back to the domain name registrar and adjust the nameserver settings to those given to you by your hosting support.
    The distinction is relevant because many times the hosting company is NOT the same as the domain registrar.
    You may need technical support from BOTH your domain registrar and hosting company.

    Are the plugins and code that register the shortcodes active and working ?

    Using version 4.8.x rather than 4.9 will not be relevant.

    No need to purchase the pro version on this basis. The WordPress customizer is quite capable to do this.

    The best people to get your SSL certificate through is your hosting company, this way they will look after the installation for you.

    The verification takes on different levels, for one client of mine it meant that an international accounting firm (Dunn and Bradstreet) had to verify their corporate registration, that their details matched the phone book listing, and so on. Not everyone needs this, the cost was many times (10x) that of the name registration.
    I would expect that when you purchased your domain name, the transaction did not go much beyond:
    A) you want name “lonestarweathercenter.com”,
    B) No one else has it registered at the moment.
    C) Your credit card was good for the $12 or so required.
    D) You agree to some rules like keeping the contact email address up to date.
    In which case I am curious as to just what has been verified ?

    Presently the only certificate on your site is for the hosting company, for some usages like sending secure email or secure file transfer, this is enough.

    Login to your dashboard, then in customizer > additional css, add this css snippet:

    .widget {
        border-bottom: 0;
    }

    This will fix both the lines.

    Often these search controls etc are in the default widgets.

    Also you should NEVER change the theme files for just the reason you have found, the changes will be lost when the theme is updated. To prevent this you should use a child theme, details here:
    http://codex.wordpress.org/Child_Themes

    There must be a filter that can do this.

    As a debugging technique I find that displaying the full details of a structured variable is very rewarding. Accordingly I would be using debug code like:

    
    echo '<div>string is:' . print_r( $string ) . '</div>';
    

    It will show you what is in $string it it is a simple string or integer, an object or and array and what the elements are in the array.

    Laying out youe code to make it more readable:

    <?php
     $project_id = $_SESSION['project_id'];
     global $wpdb;
     $string = $wpdb->get_results(
      "SELECT reward_details FROM wpxa_rewards WHERE project_id = $project_id"
     );
    
      $someArray = json_decode($string, true);
    
        $count = count( $someArray );
        for ( $i = 0; $i < $count; $i++ ) {
     ?>
    
    <div class="panel panel-default">
      <div class="panel-body">
         <?php echo $someArray[$i]["reward_title"]; ?>
      </div>
    </div>
    
     <?php } ?>

    The problem you describe is now apparent:
    You are only selecting “reward_details” but trying to display “reward_title”.

    A more serious problem is that you are vulnerable to an SQL injection attack.
    You must never ever in your whole life EVER pass user input into SQL queries. With a browser inspector or other techniques a bad person could send your code a value like:
    $_SESSION['project_id'] = "1; drop table; AND it could be much worse.
    The solution is to use “prepare” so that mischievous input is not executed.
    More details here:
    https://codex.wordpress.org/Class_Reference/wpdb

    The certificate people are seeing says:
    The certificate is only valid for the following names: *.hostingplatform.com, hostingplatform.com
    These are the domain names of your hosting company, no one can tell that you are their client, hence your domain name remains unverified and hence unknown. This is why your website is untrusted.

    You can either buy an SSL certificate, or if your hosting supports the required ACME API, then you can use free certificates by letsencrypt, details here:
    https://letsencrypt.org/

    Your suggestion that WordPress is in a position to issue certificates is difficult to understand.

    • This reply was modified 8 years, 3 months ago by RossMitchell.
    Forum: Fixing WordPress
    In reply to: checkbox

    Most likely is that you do the checking and UI presentation live in the browser using javascript. If necessary the javascript can query and update the database using AJAX.

    Not a WordPress site.

    To answering questions like this, just use your browser inspector and view the <head> block of the web page.

    This is what I would do:
    Firstly, have you checked that the css and html are well formed ? Browsers vary considerably as to how they deal with irregularities, some seem to say “I get what you mean”, while a stricter one says “not doing it”. Use one of the online testing sites like:
    http://validator.w3.org/
    http://jigsaw.w3.org/css-validator/
    I see errors like: “Element blockquote not allowed as child of element ol in this context.”

    If you are still stuck, then, using the browser inspectors in safari and say firefox, I would compare how the composing blocks/paragraphs etc (div and p) are behaving. How are they nesting and spacing, how do they flow ? I would probably even sketch what was happening.

    How fonts render can vary on the fonts available, same as to which weights are available. For example “font-weight: 400;” may render the same as a weight of 500, while on a different browser it jumps to a heavier render.

    In my Linux – Ubuntu system the website configuration files live at:
    /etc/apache2/sites-enabled/ in files like 001-local
    Where are your site config files ?

    The directory it was complaining about is <dot>snv the “.” prefix makes it a hidden file. Turn on show hidden files and it will be there, or “ls -al” will show it too.

Viewing 15 replies - 721 through 735 (of 3,259 total)