Posts by ParkerAndKent

Guys, just don’t call your themes with simple common words, you can’t own a common word. Give your themes an original name and then will be harder to see a new theme with the same name… and if then happens would be easier to dispute the intellectual propery of the product name.

LOL

Would be nice to have a site where authors (that are everywhere in the world) could share info about accomodation and services in their home towns…

We can help each other to enjoy our life. I imagine a community site where authors can post their town photos and info, help other authors finding cheap accomodations (friends appartments for example), drive from/to airports, meet each other and have fun together for some days, etc…

I’m just chilling like a villan, but this isn’t a bad idea

I travel a lot and especially when I go somewhere for a weekend the most hard thing is to enjoy the places like normal people, I dislike to be and feel a tourist and just walk around the monuments…

I’d love to meet someone that shows me the normal places and how people live the real life!

MNKY said
Hi, you try this to enable timthumb use for multisite: LINK Cheers

Mmm, the problems are others with multisite. Is not about allowing external domains, but rewriting the upload dirs that are in a different location and with different names than normal for each blog.

paulmc said
Actually, that brings up a good question. All we are really trying to accomplish is to have one login for several themes so our readers don’t have to login twice to comment. Any suggestions if we remove it from the multisite theme?

In the specific, you need an Extended License only if you allow your users to activate the theme (London Live) for their blogs… if this isn’t the case a Regular License is enough. Just don’t network activate the theme or allow your users to activate a personal blog. If it’s just for the comments, you’re good to go with the RL

For the images paths contact the author and check if he’s available to edit the theme files to allow the theme on MU installations.

Cheers,

Parker

paulmc said
I’ve read all the posts I can find about Tim Thumb problems but find none concerning multisite. I have London Live running on our server just fine and another copy running on the same server, only on the multisite platform for Wordpress and the images don’t show.

We’ve made sure all the permissions are the same as the one running on a standard Wordpress install – all on the same server with the GD library installed.

Any ideas?

Hi,

when in multi site the way to retrive the images paths is quite different and probably the theme you’re using doesn’t support it. So the problem isn’t strictly related to timthumb, but to the way the images paths are constructed (because the rewrite rules).

My new themes support MU installations, but the way I implemented it for sure can’t be applied to other themes, so I can’t help about this in the specific. For more info contact the theme’s author, but also consider that for multi users installation you would need an Extended License of the theme

Parker

mpc said

JamiGibbs said
You probably want to use get_the_term_list

Something like:

get_the_term_list( get_the_ID(), 'portfolio_cat', "Category: " ) 

Strange but this doesn’t work either :/

P.S It doesn’t even display the “Category: ”

Do you do echo before the function call? The WP functions that start with get_ need to be called after an echo, the ones thet start with the_ don’t (eg. the_title())

Parker

LandonWilson said
I think of code as a fine italian car (which I figure P&K knows something about) – every little detail matters, and even if a normal person wouldn’t see it, you know it’s there, so you should make it perfect. How can you have such attention to detail with copied code?

I’m italian and I take care of everything… just look at the HTML output of my themes, also the widgets are re formatted to look readable and with the right indentation…

I don’t think in the world there is a WP theme that comes with the same clean output my framework generates.

I know it’s a basically useless thing, but it makes me feel better and if I need to read the HTML of my themes is way easier

Usually I review all my code after months to find an extra space between the lines, or an if statement formatted differently than others… I’m a maniac and I think I’m also obsessive-compulsive about code

I’m proud of myself and my work and I’m happy like this

Parker

I’ve written each single line of code by myself… and the whole framework is huge. I don’t like to use other people’s code, because:

1: I like to code

2: I like my code

3: I don’t always trust code that I’ve not written myself, also if mine isn’t better

4: I can find the right line of code that is the cause of an issue in a few seconds, because I know line by line everything that gives life to my themes.

5: Other authors can do what they want, I’ve seen many themes that are just a collage of code found here and there… just looking at the code style of each function you can understand that

6: Is unethical to use code of themes on sale here to create other themes to sell here, unless the pieces of code are from common libraries available online.

This is my vision.

Obviously the php tags get screwed here, I really can’t find a way to post them in a readable way…

Mmm,

you should define some constants in your plugin, something like this:

if ( ! defined( 'YOUR_PLUGIN_BASENAME' ) )
    define( 'YOUR_PLUGIN_BASENAME', plugin_basename( __FILE__ ) );

if ( ! defined( 'YOUR_PLUGIN_NAME' ) )
    define( 'YOUR_PLUGIN_NAME', trim( dirname( YOUR_PLUGIN_BASENAME ), '/' ) );

if ( ! defined( 'YOUR_PLUGIN_DIR' ) )
    define( 'YOUR_PLUGIN_DIR', '../wp-content/plugins/' . YOUR_PLUGIN_NAME );

and define a plugin function (in the right way) that prints the js var of the path in the admin head:

function your_plugin_head() {
    if ( defined( 'YOUR_PLUGIN_DIR' ) ) :
?<

<script type="text/javascript">
    var your_plugin_path = '&lt;?php echo YOUR_PLUGIN_DIR; ?&gt;';
</script>
&gt;?php
    endif;
}
add_action('admin_head', 'your_plugin_head');

Then you should be able to get the path (whatever the folder name of the plugin is) in your js script:

alert(your_plugin_path);

I didn’t test it, but should work.

Parker