cnanders
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Run two domains from same database contentAll,
For what it is worth, I ended up giving up on this. I spent a lot of hours trying to get it working with no luck. I’m stuck with dumping the production database every so often and uploading it to the development server, changing the ‘home’ and ‘siteurl’ fields inside wp_options.
If anyone comes up with a solution I’d love to hear it.
Forum: Fixing WordPress
In reply to: Run two domains from same database contentFair enough.
In general I know this is not something most people would like to do b/c if you mess something up in the development environment, your production site is hosed. But I’m in the ‘build’ phase of a large website (it is not live yet) so this would be a nice feature.
Thanks for the reply.
-ChrisForum: Plugins
In reply to: [Plugin: Contact Form 7] Email submission successful but no mail receivedHi gsiroland,
I recently installed WordPress and BBPress and was experiencing similar issues with sending mail through PHP. Then today, at 3:45, I got all of the emails at once just like your previous post:
Update: Several hours later all of the submissions suddenly arrived in one fell swoop. Makes we wonder if there was something wrong and/or misconfigured at the provider’s end (which for the sites in question was GoDaddy).
Did you ever figure out what the issue was?
Forum: Requests and Feedback
In reply to: WordPress.org WebsiteThanks for this info:
http://wordpress.org/support/topic/415075?replies=48
or here:
Contributing to WordPress
I will let them know my ideas.
Forum: Requests and Feedback
In reply to: WordPress.org WebsiteFound what I’m looking for:
http://codex.wordpress.org/Developer_DocumentationForum: Requests and Feedback
In reply to: WordPress.org WebsiteClayton,
Of course I found those links.
I would love to see a simple API-like set of methods / classes / etc with examples that show how to integrate the WP framework into my existing site.
I couldn’t find this anywhere. One example is fine, but I’d love to see lots of examples – kind of like the jQuery.com website. And the pages you link above have “the Loop” terminology… hardly a ‘developer’ page. My point is that it seems like the WP docs are geared to a two-tiered audience, and they could make it a lot better for both by separating it.
Forum: Requests and Feedback
In reply to: WordPress.org WebsiteSORRY ABOUT ABOVE CUT OFF! — I went to Chipolte.com and Flash caused Safari to crash. I’m sure Steve would love to hear that. Back to my post
////////////
I am a web developer. I came to wordpress.org because I am interested in integrating the wordpress framework into my existing site. I found it to be a frustrating experience (the learning part), mostly because at wordpress.org it was hard to find the information I wanted.
I see it this way: WP basically has two customers
1) The person who knows nothing about web development. The “layman”
2) The experienced web developer. The “developer.”The information WP displays to these two (very different) customers (regarding use / integration) should be very different. For example, all of “the Loop” lingo is laughable to a developer, yet I understand it is completely necessary for the layman.
What I would LOVE is a “How WP works. How to use it. How to integrate it.” page that is split into two columns
COL 1: <h1>I know nothing about web development. Speak my language.</h1>
COL 2: <h1>I know PHP, MySQL, CSS, HTML,… give me the real deal.</h2>
And from here, the “layman” and the “developer” are directed to different pages written with a completely different tone / vocab / etc. Being a developer, I would love to see a simple API-like set of methods / classes / etc with examples that show how to integrate the WP framework into my existing site. I mean, really, what developer wants to use a canned WP template? Probably not many. So this information should not be front and center.
That said, the layman doesn’t ever want to see the words “class” “method”, etc. They care about templates, themes, blah blah.
Anyways, this distinction wouldn’t be hard to make, and I think it would help BOTH types of WP customers by hiding the information each of them are not interested in reading.
Sincerely,
Chris