airfoil

Still no luck. I appreciate the support and followup. For my current project, I’ve pivoted to a different solution, but will certainly keep your plugin in mind for other projects. As mentioned, the MySQL approach seems to be a good workaround.

Thanks. I’ll see if the updates work. As mentioned, I can get it to works as expected using MySQL for some reason, so can fall back on that if needed.

Yes. I originally had it running using a fresh, basic install of WooThemes Canvas. But then, thinking there may be something theme related, cycled through twentythirteen, twentyfourteen and twentyfifteen. Same error on all three.

I should note that when I imported my CSV into a MySQL table and used:

[gdoc key=”wordpress” query=”SELECT * FROM my_table”]

The error disappeared and the table rendered as expected.

Thinking it could be something to do with the formatting of my CSV, I tested using a very plain CSV file:

one,two,three
four,five,six
seven,eight,nine

Same error. As previously mentioned, the error is also thrown when I point to the demo CSV file you use in your documentation.

For now, I’ll likely either go the MySQL route if I use this plugin, but it would be great if there is a solution to the CSV issue. Thanks.

Ipstenu: Wow. A lot to digest, but a remarkable resource. In particular, the Output Buffering section. Not sure I fully have my head around it, but definitely gets me going in the right direction. Thanks.

Nickyboy: Thanks – I’ve looked at DeployMint, but it really only deals with content, and doesn’t address architectural changes such as widgets, sidebar content, etc.

Andrea: Thanks. It seems clear that a multisite deployment is not an easy thing for staging. In our scenario, we have marketing and other stakeholders who need to contribute to a redesign. Since the only decent way to deal with this currently (from my experience) is to have a local install, I use MAMP and manipulate the hosts file so that things can be migrated easily without having to deal with changes to the domain name. Unfortunately, this means everything needs to funnel through a single point, and does not make it easy for a team to contribute. Really inefficient. The other approach I’ve used is the WordPress Search and Replace Tool. Since it accounts for serialized strings, it is a great, great thing for multisite developers. However, I still get a little queasy running this against a big database, fearing something will go sideways. I’ve done it, and it seems to work really well. But…

My real wish is that WP would not rely on having the FQDN embedded into the core data.

Out of curiosity, from your extensive experience in this area, is there some technical reason that the WP development team deals with things in this way, rather than using some sort of variable scheme in place of the primary domain name?

Thanks, Andrea. Unfortunately, this is a true multisite environment, where there are about a dozen existing production subsites in addition to the existing primary.

My hope was that there was a straightforward solution to having a staging subsite that could be “easily” migrated to replace the primary site. I’ll search on Ipstenu’s posts and see about the issues regarding the blog ID. And if I come up with some magic method, will post back. Thanks again, all.

One other thought: Is there any way to (or danger in) manipulate the htaccess file so that the primary (mydomain.com) actually points to a subdomain (staging.mydomain.com). I suspect that would start getting into some complex things that could easily go sideways, but…

Rod: I wish it were that. : ) This is a multisite issue – running 3.3.

Andrea: The core issue is that there is a team “redesigning” the main site – so in addition to content, I’m dealing with widgets, plugins, layout issues (same theme, but I use a framework system), etc. Typically on multisite installs I work with a local version (running MAMP) and change my local host file so that I don’t need to deal with any domain name changes in the database (my type of work deals with small multisite installations that are specific to some specialized content publishing – rarely with more than a dozen or so subsites).

When doing these sorts of redesigns, I need to have a non-local install to which various people can contribute. Moving content is easy enough, but it is all of the extra stuff.

I’m curious if there are any suggested methods for replacing these types of elements on the main site, with the product of a “staging” subsite.

I should also mention, that I’m dealing with a non-technical group – so solutions that would include code repository check-in, check-out and that sort of thing would likely be a non-starter for them.

Thanks – I’m very much looking forward to seeing this installation get upgraded to 3.x. However, as of now, it is still 2.9.2, and deleting the user from the Site Admin > Users panel appears to only delete them from the primary blog/site. In my testing, a user deleted from here still remains in the other blogs.

As a result, I’ve found myself looking for what appears to be a more complicated solution…

Thanks – I did post over there, but got no response.

I think my mentioning the xprofile bit was a bit of a red herring here. I’m pretty sure I can figure out how to pull a list of users by a certain xprofile field.

What I’m mostly wondering about is how to loop through a large list of users (once found) and completely delete them from ALL blogs in a WPMU installation – but do it in a responsible way that triggers whatever needs to be triggered in WPMU when a user is deleted.

Unfortunately, this particular installation is still on 2.9.2. They are in the process of upgrading, but rely on several custom plugins and themes that need work to get them into 3.x shape.

That said, certain groups of users that need to be removed completely from the system belong to many blogs – typically 5 to 10 – and there is really no way in WPMU to isolate these groups and remove the users from all blogs in the system (at least not as far as I know) without out going blog-by-blog, user-by-user.

Thanks again.

Thanks, Andrea. I figured out the issue. All of our servers have DNS managed at the host – or so I thought.

Apparently this particular server (due to some legacy application issues) was having DNS managed at the registrar.

Although I had wildcard DNS set-up at the host, it didn’t matter because the host DNS servers were not authoritative for the domain.

Took me far longer than it should have to get to the bottom of it.

Thanks for your help, Andrea – always appreciated!

@pmagony:

I wish I was able to provide some insight. The only thing I might suggest is to make sure there is a default owner set for new web leads in SF. Not sure if this would cause the problem, but it couldn’t hurt to check.

Also, I think you can generate a straight HTML form via SF for web leads. You may want to try that. If that doesn’t work, it would rule out an issue with the plugin, and isolate it to SF settings.

FWIW.

FWIW…

Problem solved. I was unaware that the Web-to-Lead functionality needs to be explicitly enabled via the Salesforce.com administrative settings, and a default “owner” for new web leads defined before Salesforce will accept the web-generated lead. (Setup > App Setup > Leads > Settings)

I assumed that it would work automatically and didn’t realize the need to tweak any settings in Salesforce prior to installation and use.

Just wondering if you were able to figure out the problem you were having. We’ve installed this plugin, and are having the same issue. We’ve correctly entered our SF organization ID, and get a success message when the form is submitted, but nothing appears in Salesforce.

Thanks, Godfrey.

This situation is happening with site admin users, and has not been reported with other elements. That said, the users in question are working from a location in another state, and I’m only going by reports and what I’ve seen when I log in and look at the widget after they attempt to add HTML into the section widget.

I’m not actually suspecting the widget/plugin itself, since I can’t replicate the problem from my end – just wondering if anyone had experienced anything similar and had any ideas about where to start looking.

Thank again – I appreciate your response.

Just saw some code in another post that included a “show_home” parameter – which provides the needed functionality.

However, there does not seem to be any mention of this parameter/option in the Read Me, nor in the list of options on the plugin page. FWIW.