Tag: WordPress (Page 177 of 220)

When it comes to parsing CSV files, the way you go about doing it is relatively the same (hence the need for the standard format, right?):

1. Read the file
2. Break each line into an entry into a collection
3. Iterate through the collection
4. Create an object or element with attributes based on the data in the current given line

Sure, this is a high-level view of how it’s done, and your specific implementation may have finer nuances, but – as I mentioned – I think its safe to say that the way we go about parsing a file is the same regarding of what we do with the data once we start reading it.

When you’re working on an implementation of CSV parser and you’re accepting data from an upload, then there are several things that need to be checked such as the validity of the file type.

For example: If a person uploads an image, you don’t want to proceed with parsing it; however, if they upload an actual CSV, you obviously want to process the file.

But this can be tricky depending on the operating system.

Continue reading

Comments are closed on this post. Let's keep the discussion on the Make WordPress blog.

Earlier this year, I drafted the first version of the WordPress JavaScript Coding Standards (and I discuss it more in-depth in this post).

When I contributed the first version of the standard, the conventions were based largely on writing vanilla JavaScript, and on the existing WordPress PHP Coding Standards; however, there has recently been a surge of interest in continuing to develop the JavaScript Coding Standards.

Because I obviously have a strong interest in this, because I believe that more and more sites and applications are doing more work on the client-side, and because I want there to continue to improve the existing WordPress codebase, I wanted to make sure that there is about to be a major update to the JavaScript coding standards.

Continue reading

Ask anyone who’s involved in the WordPress community – and who has been for sometime – and you’re likely to hear that it’s a great experience not only because of the projects that are being built on and around WordPress, but because of all the people involved in the economy and in the community.

And it’s true: Being a part of the larger WordPress economy and community is exciting.

But, like with anything else, it’s challenging at times. I think that anyone who has stuck around long enough knows that as much we we all want the best for WordPress – I mean, we even enjoy hanging out with our competitors.

On the flip-side, we also get stuck in the typical Internet flame war arguing over what technology should be used for what all the while forgetting some of the larger problems at hand.

We’re only human, so it’s bound to happen, right?

It’s a weird thing, for sure, but it’s the nature of the community – at least for now (and probably for longer, if you’re a cynic) – but that doesn’t mean that you – or anyone else – should be dissuaded or discouraged from becoming a part of it.

But there is something that I’ve noticed in the community, or around the fringes if that’s what you’d like to call it, and sometimes I think people’s desire to be known – or wanting to achieve some type of WordPress fame or notability – outweighs the work, the contributions, and their input into the economy.

And though one could argue there are many problems with that, one of the largest is that the focus is being misplaced for the sake of the individual rather than improving the core product or products around WordPress.

Continue reading

When it comes to pricing WordPress plugins, this isn’t exactly new territory. In fact, I’d say when it comes to pricing any online service or product, there are already tried and true ways that prove to be useful given certain scenarios.

It’s basic economics, I suppose.

So this post isn’t so much about various ways to go about pricing WordPress plugins, but what opportunities we have as developers, designers, companies, and so on as the WordPress landscape continues to change.

Continue reading