Forum Replies Created

Viewing 15 replies - 211 through 225 (of 496 total)
  • wpismypuppet

    (@wordpressismypuppet)

    You are welcome… Glad I could help out. I’ll have to consider that “help business”. 🙂

    Also, please mark this as resolved so others know it’s all set. Let me know if you need anything else.

    wpismypuppet

    (@wordpressismypuppet)

    If you want to use WordPress outside of WordPress you simply need to require() wp-load.php, which is found in the root of the WordPress installation. Since your site is in a sub-directory, you’ll want to look in that folder. Then you’ll call the search form where ever you want it. So something like this:

    <?php
        require( 'subfolder/wp-load.php' );
        get_search_form();
    ?>

    Things to pay attention to…

    1) The path inside the require() function will change according to where you are relative to where the wp-admin.php file is. Also, replace “subfolder” with your actual folder name :).

    2) The require() function need only be called ONCE per page it’s used on. In fact, I use require_once() as it does the same thing, but does a check to make sure the file hasn’t already been called. Just a safety measure on my part.

    3) Though the require() function CAN go anywhere, it’s generally good practice to place it a the very top of the file. This means you would separate the get_search_form() function from the require() function, as you’ll want the search form somewhere appropriate on the page

    Let me know if this makes sense. Good luck.

    wpismypuppet

    (@wordpressismypuppet)

    I should mention that if possible, you should leave the 301s in place indefinitely, as anyone linked to your site from somewhere else will get a 404 once you delete the 301s. And in that case, your SEO will take a hit losing all those linked people (has nothing to do with Google, and only you know if people are linking your website through SEO tools).

    However, it may not pay to keep a whole domain for this reason. Weight carefully the money vs. the ranking and make a choice.

    wpismypuppet

    (@wordpressismypuppet)

    No problem… you can check out this tutorial:

    http://www.bruceclay.com/blog/2007/03/how-to-properly-implement-a-301-redirect/

    It has some humor in it, but it’s right on the money. You basically need to open your .htaccess file in the root of your website and add something like:

    Redirect 301 /chimney-balloon-inflation-tube-2/ http://purchase.ie/chimney-balloons

    to it. Keep it all on one line though… spaced appropriately. That’s all there is. Now, anyone linked to the old page will get redirected to the new page. And Google will re-index while keeping your ranking!

    The only thing to pay attention to is the .htaccess file. I don’t know how much experience you have with them, but I’ll assume none 🙂

    WordPress will already have a .htaccess file in your root folder. It’s done by default. So you can just edit that one and not worry about creating a new one. However, if you FTP and don’t see one, then it’s probably hidden. Any file that starts with a period (.) is hidden. Since .htaccess starts with a period, it’s hidden 🙂 Your FTP program will have an option somewhere to “show hidden files”. Make sure it’s checked and you should be in business.

    BACKUP THIS FILE FIRST… in case you make a mistake. And DON’T play with anything in the .htaccess file unless you know what you are doing… just add the above code to the end of the file, and leave a blank line below it.

    wpismypuppet

    (@wordpressismypuppet)

    Weird… I’ve changed the title of many WordPress pages and the permalink has never changed on me. Typically you’d have to manually do that. So for that, I have no answer. What you could do is go back into that page and physically change the permalink back to what it was. This will correct the problem in Google. You can have a title that is different from it’s permalink.

    If you wait long enough, Google will purge the http://purchase.ie/chimney-balloon-inflation-tube-2 and forget it ever existed. It will also index http://purchase.ie/chimney-balloons and the world will be in harmony once again.

    Except… any and all SEO associated with http://purchase.ie/chimney-balloon-inflation-tube-2 will be gone and you’d have to start all over again! Since you claimed the page ranked pretty high on Google, this is not a good thing for you.

    So two options to save your SEO: a) manually change the permalink on that page to what it was or b) set up a 301 redirect to move all traffic pointing to http://purchase.ie/chimney-balloon-inflation-tube-2 to http://purchase.ie/chimney-balloons. If you need info on how to do that, I can shoot you a few links. I just helped another fellow out with 301 redirects not 20 minutes ago!

    Good luck and I hope I answered your question.

    Forum: Fixing WordPress
    In reply to: JSMin.php
    wpismypuppet

    (@wordpressismypuppet)

    JSMin.php is a modified version of JSMin by Douglas Crockford. It basically allows you to compress/minify your JavaScript files to make them more compact to make them faster to download. It’s older stuff, and there are millions of compressors out there. Find one that works for you and use it. Or use this one. Six to one… half a dozen to another!

    If you aren’t the sort who compresses JavaScript files and CSS files, you should 🙂 It’s good practice… but there are guidelines, like everything else, you should read up on and follow. Especially in this day and age where more people surf the web on mobile devices than actual desktop/laptop computers!

    wpismypuppet

    (@wordpressismypuppet)

    Good on you for getting it so quick! Glad I could help…

    wpismypuppet

    (@wordpressismypuppet)

    @doomnezeu

    While your method WILL work just fine, it will absolutely kill any and all SEO you might have already for your website. Your method is only a good option if you don’t care about SEO.

    wpismypuppet

    (@wordpressismypuppet)

    You want to put the redirects here:

    oldone.com lives at /oc and has its own .htaccess file.

    You will have to leave the old domain up for a bit, until Google has indexed all the new stuff. Of course, delete all the files and just leave the .htaccess file. After a month or two, kill the old domain completely.

    If your file structure is exactly the same from domain to domain (ie. olddomain.com/myfile/ -> newdomain.com/myfile/) then you can do a simple:

    redirect 301 / http://www.newdomain.com/

    If ANY of the file structure has changed… then you’ll need one redirect for each page that has a new file structure. For example, if you had olddomain.com/myfile/, and the new structure is newdomain.com/myfolder/myfile/, then you’ll need:

    redirect 301 /myfile/ http://www.newdomain.com/myfolder/myfile/

    Again, one of those for each page that has a new home. The very last line in your .htaccess file would be the:

    redirect 301 / http://www.newdomain.com/

    From above… keep in mind that you need a blank line at the VERY end of the .htaccess file. Read this document too… talks more about SEO reasons and has more details. Plus a little humor 🙂

    http://www.bruceclay.com/blog/2007/03/how-to-properly-implement-a-301-redirect/

    wpismypuppet

    (@wordpressismypuppet)

    If you are running on an Apache server with rights to create an .htaccess, all your problems will simply vanish! Follow these rules:

    http://jesperastrom.com/seo/how-to-do-a-htaccess-301-redirect/

    We’ve had to do this many times in our career. This is the best approach to keeping SEO in tack.

    wpismypuppet

    (@wordpressismypuppet)

    Are you already getting the URL of the image? Can you show a little code? If you already have the URL of the image in a variable like:

    <?php $image = pathofimage; ?>

    Then you can use the PHP function basename() to get just the filename. Like this (using $image from above):

    <?php $filename = basename($image); ?>

    wpismypuppet

    (@wordpressismypuppet)

    If I were you… I would use query_posts() on my index.php page to alter my main loop to exclude the native language posts. This will keep everything working like normal, but users won’t see native language stuff.

    Then, I would create a custom page template in which I would again use query_posts() to create a custom loop that would only gather the native language blog items.

    Give that a shot and let me know if I can offer more assistance. It’s not that tough, especially since you have PHP experience, and the pages I gave have ample examples.

    wpismypuppet

    (@wordpressismypuppet)

    Doing a super quick Google search, I found this to do the ordering:

    http://zupplerworks.com/

    and this to show a bunch of themes that do restaurant business:

    http://www.tripwiremagazine.com/2012/07/wordpress-restaurant-menu-templates.html

    Good luck with your research!

    wpismypuppet

    (@wordpressismypuppet)

    First, thanks for offering to buy me a beer! I do the work on here because I enjoy helping people and my business makes WordPress sites on a daily basis. Instead of a beer, just spread the word about the company I work for! The info is at the website associated with this account.

    As far as the 500 error is concerned… the code I gave you is JavaScript, not PHP. You should really just add it to the footer, or better yet, do it properly through wp_enqueue_script().

    For simplicity, just add it down in the footer before the close body tag </body>. Also, since it’s JavaScript, you’ll need to enclose all the code in script tags, like so:

    <script type="text/javascript" language="javascript">
    // Loop through each category list item's anchor tag
    jQuery('.cat-item a').each(function() {
        // Add the rel attribute
        jQuery(this).attr('rel', 'tooltip');
        // Get the title
        $title = jQuery(this).html();
        // Add the category title as a title attribute
        jQuery(this).attr('title', $title);
    });
    </script>
    wpismypuppet

    (@wordpressismypuppet)

    Are you familiar with folder permissions and how to change them? You basically just need to chmod permissions on the uploads folder to 0755. You may need to make it 0777 if 0755 doesn’t work. And if neither work, trying chmod permission on wp-content itself to the same values.

Viewing 15 replies - 211 through 225 (of 496 total)