Forum Replies Created

Viewing 15 replies - 16 through 30 (of 496 total)
  • wpismypuppet

    (@wordpressismypuppet)

    Add the “autoStart=false” parameter to the videos…

    http://support.brightcove.com/en/video-cloud/docs/player-configuration-parameters

    I don’t use this service, but all the documentation indicates that by default the players start ‘stopped’ and you have to enable autoplay. With that said, check how you are creating your players…

    wpismypuppet

    (@wordpressismypuppet)

    Why not just set the WP_POST_REVISIONS option in your wp-config file?

    http://codex.wordpress.org/Revisions

    Anything older than the number you set are automatically deleted.

    Thread Starter wpismypuppet

    (@wordpressismypuppet)

    Hey David,

    This solution looks like it helps Michael Nolan more than me. What it looks like your code adjustment does is makes sure that all the children of a parent inherits the sidebar. And that’s a great solution as it could potentially be an issue.

    My concern, however, is to STOP propagating the sidebar down to the children, if I so choose. Currently I have no choice other than visiting each and every child page and choosing a different sidebar. If I don’t want the children to have a sidebar at all, there is not way to stop this.

    My suggestion is to leave the code exactly how it is… and let it continue to run the same way it currently runs (so as not to break current websites). However, all I’m suggesting is when you visit “Appearance->Custom Sidebars”, and you see all of your sidebars listed in the section “All the Custom Sidebars”, there be a check box to STOP the children pages from inheriting this sidebar.

    By checking this box, you essentially makes the sidebar only appear on pages you physically visit and choose to use this sidebar. It essentially removes any automatic inheritance. This method is a good solve because a) it keeps everything running exactly as it currently does and b) give the option PER SIDEBAR to make the sidebar lose inheritance if so desired.

    In fact, that snippet of code you sent me is probably where to do it. Just add a check box per sidebar to store the value “on” or no value at all. Then in your snippet add an extra check for that value. If it equals “on”, don’t do the $replacements piece. If it’s an empty value, continue on.

    Again, if you need some help in writing the code, I’d be happy to assist. I as only because you are more familiar with your own code and would probably be able to do this much faster. If you would like help, I can start digging through and share what I find with you.

    Please let me know if this helps and makes more sense. I appreciate your help with this, and your willingness to listen and apply changes and updates to your code! Thanks again.

    wpismypuppet

    (@wordpressismypuppet)

    Well, it’s only a bug if you create a child theme and THAT get’s overwritten. You should never make changes to any of the themes themselves, you should only ever make child themes so your work doesn’t get lost!

    https://codex.wordpress.org/Child_Themes

    wpismypuppet

    (@wordpressismypuppet)

    If you have the shortcodes, then they ARE of use. Use do_shortcode(). I use it all the time in my PHP template files.

    wpismypuppet

    (@wordpressismypuppet)

    Thread Starter wpismypuppet

    (@wordpressismypuppet)

    Hi David,

    I am aware that I can override the parent sidebar by going into a child page and selecting a different sidebar altogether. However, what I am looking for is a way to opt out of the parent inheritance! So basically, if I have a parent page, and I choose a sidebar for that parent, all of it’s children will have the same sidebar (unless I visit each child page and select a different sidebar). But what if I don’t want the child page to have ANY sidebar? How do I stop the parent from propagating down to it’s children?

    In your version 0.8.2, this was not an issue as the parent page’s sidebar didn’t trickle down to the children. So what I was asking for is a mix of the old and the new. Leave it the way it works, but when you visit the custom sidebar page (where you create custom sidebars) offer a check box for EACH sidebar created to disable parent inheritance. This way, by default it will propagate down to the children. But if you check the box, the children won’t have any sidebar unless you visit the child page and say otherwise.

    Does that make more sense?

    wpismypuppet

    (@wordpressismypuppet)

    Hi there,

    It seems to me this may very well be a Firefox bug, however…

    The reason things are breaking is because your theme, dt-the7, is using the Pixastic library to do some canvas manipulation and other things. They clearly state on their website that it “is an experimental library which allows you to perform a variety of operations on images…”. Experimental be the key word here.

    Keep in mind as well that canvas is fairly new stuff as well. It appears that Chrome and other browsers handle the canvas much nicer than Firefox, which has been the case for some time now. Not to say that this code won’t work, but you can see why there might be a glitch or two.

    Here’s what I surmise… and my opinion is worth about what you paid for it:

    Your site loads extremely slow… I’m gathering it’s because of the really large images you are using, along with all the JavaScript being thrown at the user as well. To me, it “appears” that in some cases (when the glitch is happening) that the JavaScript is trying to draw a canvas or utilize a part of the website BEFORE that part of the site has finished loading.

    A possible fix to your problem might be to properly defer the loading of this JavaScript. I don’t know if this will work, or if you even have access or rights to do this being as it’s not your own theme, but it’s worth a shot to test.

    Another option might be to invoke some proper caching plugin to make it all load faster. This also may fix the issue, but I’m not sure about that.

    All in all, you are using some pretty cool, pretty advanced stuff that is all experimental. Is it worth it to you to have your site in that condition? That’s personal preference. Your site will not work on many versions of Internet Explorer, and completely craps out when JavaScript is disabled. To me, that’s a no no. We should be using JavaScript to enhance our sites, but not to rely on JavaScipt to run the website. There should be some form of fall back… always.

    wpismypuppet

    (@wordpressismypuppet)

    If you are getting “Array”, you can do this to see what’s inside the array:

    echo '<pre>';print_r($key_1_values);echo '</pre>';

    Echo won’t work on arrays, but a print_r will dump the contents and show the keys. Also, the <pre> will format it nicely so you can see what’s going on instead of keeping everything on one line.

    My guess is it’ll be an empty array. If you remove ‘price’ and just pass the id, your array will contain all meta data for that id, so at least it won’t be an empty array and you might find what you are looking for with the code I provided.

    Has anything been entered in the price field for that post?

    wpismypuppet

    (@wordpressismypuppet)

    Look, I’m not trying to be argumentative or even insulting, but what you are asking for is a fix that does not exist with over 98% of all WordPress users. The reason it doesn’t exist is because all hosting companies offer a later version of PHP which fixes any and all issues you are talking about. The reason you experienced this problem is because your hosting company wasn’t proactive in getting everyone in their system up to snuff. If you want to point fingers, I guess that would be a good place to start.

    On a second note, asking to create a fix to a problem that only occurs in obsolete situations is like asking you, as a Windows programmer, to make sure your application accommodates a bug found only on Windows 3.0, released in 1990. It’s just not practical. The version of PHP you were using was outdated, so WordPress should not have to provide a fix to a bug for a software package no longer supported by the very people who created it!

    Only a rare few will experience your situation and there is a simple fix. Upgrade PHP, or find a new host who does that for you on a regular basis.

    The other reason it’s a rare problem is because the GIF file, though magnificent in its own time, has also become obsolete. If a user wants a simple transparent static image, they create a PNG which has far superior transparency/color properties. If the user wants an animated image for whatever reason, they can use a scalable vector graphic (SVG), JavaScript, HTML5 canvas, or CSS3 animations (note how I left out Flash… we won’t even go there). SVGs are superior to GIFs because they are vector and won’t loose any quality no matter what the resolution.

    You have a large collection of GIFs, and no one but Pioneer Valley will ask you to upgrade those images… but you should upgrade all your software to the latest versions whenever possible (and whenever stable by the developer). It’s safe, it’s smart, it’s secure, and it will open more doors for you to do more advanced things. The problem with advanced things is that they are not fully compatible across all browsers/devices, but that is what graceful degradation is for!

    wpismypuppet

    (@wordpressismypuppet)

    Yes… it is a JavaScript menu, so you’ll probably need to adjust the JavaScript as well to reflect the new height. Once JavaScript start to play with an element’s styles, the CSS file controlling those styles are overridden because JavaScript will then make inline styles. It works on the first drop down, but JS takes over from there.

    However I strongly advise you to find a better menu system. If JavaScript is disabled (which a lot of people do for security) your website is rendered completely useless. Not to mention SEO will suffer as crawlers have a harder time with JS menus. Many of your pages might not get registered with Google and the likes.

    JavaScript is nice to enhance certain aspects of a website, but it should never be used as the only means of functionality.

    wpismypuppet

    (@wordpressismypuppet)

    Looks like there are a few out there…

    https://www.google.com/search?q=wordpress+plugin+record+audio&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

    Nothing is going to do exactly what you need it to do, but at least someone has given you the ability to record audio. Tweak the plugin to fit your needs. Open source is amazing for just this reason!

    Thread Starter wpismypuppet

    (@wordpressismypuppet)

    Thanks for the quick response and quick fix! We’ve used this plugin in the past, but it had some flaws that were hard to work around. However, your hard work and dedication has made this plugin really fantastic!

    The ability to now format the content within the columns, drag and drop for different column sizes and layouts, responsive design, and the ability to go back in and reformat the columns without losing any work are major updates!

    We have added this plugin back into our collection and will use it often! It’s really become much more user friendly, not just developer friendly, which makes it easier for us to pass on to our clients.

    Thanks again for the help, and the hard work.

    wpismypuppet

    (@wordpressismypuppet)

    You would need to do device detect on the main html site and redirect people that way. Here is an answer to a question that covers all the bases of device detecting (javascript, php, etc) since you can’t rely upon just one working:

    http://stackoverflow.com/questions/9511526/auto-mobile-site-redirect

    Keep in mind that device detection is looked down upon by a large number of people (just like anything else… it’s a double edge sword). Also keep in mind that device detection is NOT RELIABLE by any means. It can easily be tricked (not that many people would do this, but you’d be surprised).

    Also, a large majority of people do not like being forced to view a mobile version of a website since their new smartphone is probably more than capable of showing their full site version just fine. It’s probably best to give the user the option instead of forcing it upon them.

    One other thing to note… it’s MUCH better to use media queries and “capability” detection rather than device/browser detection methods. For example, add functionality to your website based on if the device/browser can handle that functionality. This is much more reliable and doesn’t “sniff” the user for information.

    Read up on Luke W. and other great CSS authors to learn more (no I don’t make money off endorsing them, I just respect the movement they are trying to make). This one in particular is great, but check out his site for way more information than you’ll ever want to know 🙂

    http://www.lukew.com/presos/preso.asp?31

    wpismypuppet

    (@wordpressismypuppet)

    For what it’s worth… this is not a WordPress “bug”. This is a PHP bug. But it’s not even a bug. PHP has used the GD library for quite some time to handle image manipulation, but it’s not as good as ImageMagick. One of it’s flaws is keeping gif transparency on image resize! It also has problems with GIFs that are not 24 bit.

    What’s happening here… your current host does not support, or at least have enabled, ImageMagick natively. Because ImageMagick is not enabled, WordPress will fall back to GD to handle image “crunching”.

    When you use WordPress to upload images, WordPress sends that original image through a series of steps to make thumbnails. It uses PHP’s resize function to make thumbnails. PHP’s resize function is dependent upon which library is installed, and since you are using standard GD, you are having issues.

    The problem goes away when you FTP the image directly to the server because WordPress is not “crunching” the image through the PHP GD library anymore… so it’s not getting affected.

    Just wanted to clarify that this is NO FAULT of WordPress… it’s a problem with your host not using the latest version of PHP. Most hosting companies don’t even support 5.2 or lower anymore (actually since August 2011) and force you to upgrade.

Viewing 15 replies - 16 through 30 (of 496 total)