princekj

Thanks Mike, I didn’t know about those groups.

What I’m really trying to find out is whether or not the community would find value in a basic Product Information Management (PIM) system.

I ended up putting one together for an internal project and now I’m thinking that this is a universal problem for anyone with a good number of SKUs (>500) that needs to perform a process on each product in their shop (categorizing, writing titles, meta-descriptions, product descriptions, image manipulation and touch up, etc.).

What I’ve created is a product “assembly line” that allows store owners to upload vendor data and push that out to a scalable workforce to do the heavy lifting of performing a defined process on each product—and then once the process is complete getting that data into the appropriate woocommerce DB tables. It’s great for a startup store to seed data or for shop owners that want a better way to maintain their data.

The alternative has always been a lot of excel sheets and SQL.

Would love your feedback, I’ve been reading your articles on WooC for several years now and know you have deep expertise on this subject.

This is still not working. Problem seems to be with this scenario:

– wordpress multi-site subdomain
-domain mapping
-nginx
-wordpress installed in ./wp instead of root

Some chatter about it over here:

https://core.trac.www.ads-software.com/ticket/23221#comment:27
https://gist.github.com/danielbachhuber/9379135

Hey mika, I watched your “don’t use wordpress multi-site” video last night and I’m re-considering it for this project.

Thanks for the great content.

I’m using multi-site subdomain with domain mapping and trying to get things working locally with a vagrant box running debian wheezy and nginx 1.4.5. This is my first time using multi-site.

I had the site working fine at wordpress.dev after my 5 minute install…Simply changed the site URL under general settings and left the wordpress URL as wordpress.dev/wp

Things got weird after enabling multi-site subdomain.

Here’s my config

// ==================
//SETUP MULTISITE?
// UNCOMMENT BELOW
// ==================
define('WP_ALLOW_MULTISITE', true);

// ====================
// SETUP MULTISITE
// ====================
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', true);
$base = '/';
define('DOMAIN_CURRENT_SITE', 'wordpress.dev');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

First, my network admin panel returned 404. I had to edit line 2255 in link-template.php. My network admin was bringing me to /wp-admin/network instead of /wp/wp-admin/network

$url = network_site_url('wp/wp-admin/network/', $scheme);

Ok that solves that.

But after setting up domain mapping my first sub-domain site thinks all its resources are located in the “default” directory ./wp-content instead of skeleton’s /content

Not sure if this caused the problem but I just noticed my local-config.php didn’t have the snippet with the ABSPATH in it when I did the original install.

// ===================
// Bootstrap WordPress
// ===================
// if ( !defined( 'ABSPATH' ) )
// define( 'ABSPATH', dirname( __FILE__ ) . '/wp/' );
// require_once( ABSPATH . 'wp-settings.php' );
// =====================

Will start over and try again.

In the mean time this seems to be a recurring issue.

https://core.trac.www.ads-software.com/ticket/23221
https://core.trac.www.ads-software.com/ticket/19796
https://github.com/markjaquith/WordPress-Skeleton/issues/39

I just dropped it in /content and it works!

But…Multi-site isn’t designed to work with wordpress in a subdirectory.

So I’m having the same issue thats posted over here:

https://github.com/markjaquith/WordPress-Skeleton/issues/39

I think I just need to figure out a nginx rewrite strategy. Not really sure.