Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter dangleraction

    (@dangleraction)

    I fixed my problem of images over lapping when using Isotope by applying the image size to it’s containing div using inline css. My project uses NextGen Gallery, so it was easy to modify the template.

    Thread Starter dangleraction

    (@dangleraction)

    It looked ok and worked perfectly when I had it configured, then when I have turned “wp_debug” to true, I get a notice in the Widget’s inputfield for the title that ‘attribute_escape’ is depricated and to use ‘esc_attr()’, instead.

    A quick Find and Replace in Dreamweaver fixed that, and I can confirm that it works 100% but to get rid of the message when you have wp_debug on, just modify the plugin file and rename the method on 122 and 132.

    I guess I can speak up so I don’t have to start a new thread.

    I had Easy Modal 1.3.0.3 and the latest version of WordPress before upgrading. After the upgrade it halted everything and showed:

    Parse error: syntax error, unexpected T_STATIC in classes/admin/notice.php on line 8.

    That’s because my shared server uses a PHP version that’s older than 5.3, right?

    Thanks for providing the fix_my_modals() function. 🙂

    Edit: I tried moving the Simple Social Icons around in my Artisteer generated theme and discovered it doesn’t work in the footer.

    I used developer tools on Firefox to uncheck style properties, but I couldn’t find anything that would help. I’ll have to figure it out eventually, because that’s where I want the plugin to be. For now, I need to finish up my theme. If anyone else has time to check it out, please do and help us.

    It looks like you have it working though, skippywp. How’d you do it?

    It took me some time to find a solution, but it worked once I selected “simple text” from the widget appearance options.

    I’m learning a lot more about WordPress as I go, but I’m pretty sure there are four widget classes that you can choose from.

    Thread Starter dangleraction

    (@dangleraction)

    Hey bcworkz, a late reply is better than no reply! Thanks.

    I actually stumbled upon the WP_DEBUG feature from an online article a couple hours later. And I found the problem. My problem was I added separate <?php ?> tags for each of my functions. That made me feel kind of dumb, but it also made all my frustration and uneasiness go away. I’m really happy to know about the debug feature now. BTW, I thought I had posted on my thread that night but it must’ve never went through.

    And it’s good to know that I don’t have to add wp_enqueue_scripts afterwards. That will clean it up a lot more. Thanks.

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