WPIntell

Source evidence

Great idea

WP Essentials · review · 2013-08-15T11:13:00+00:00

praisesentiment
mediumseverity
0.67relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 32 rows with source links

18.8% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

review · 4 stars
marccrouch unresolved
We have something like this for all of our client sites and this adds a few useful features which we don’t currently have. Having a base go-to plugin for every WP install is really really handy and this has potential. Would be good if you could have the option to rename the “Client” user level to something else (e.g. Customer or Website Manager), and perhaps extend the image section with a feature to add new image/thumbnail sizes, something that comes up regularly with client installs. It did throw up a number of PHP include errors (couldn’t find certain required files) on first try but these disappeared after deactivating, deleting and reinstalling which suggests a corrupt download on first attempt. Might want to code in some more robust error-checking for things like that otherwise lay users will be freaked out by the PHP error code. Hi Marc, Can you share the errors you received? I’ve tested on a couple of different sites/servers and I’ve not seen any problems. It basically said it couldn’t find some required files and threw up a load of standard PHP include errors. After deleting and trying again, the problem disappeared so it appears there was a corrupt download on first attempt. I have amended the review now. Thanks for the feedback. Re: the include errors. The plugin was using dirname(__FILE__) to get the directory folder, but I’ve changed that in 1.0.1 and I’m just committing at the moment. Now that I’ve seen your updated message it may not be necessary but we’ll see what happens. I like your suggestions as well, will definitely look into these in a later update.

Comments

3 shown
Craig F. 2013-08-15T12:37:00+00:00

Hi Marc, Can you share the errors you received? I’ve tested on a couple of different sites/servers and I’ve not seen any problems.

marccrouch 2013-08-15T12:49:00+00:00

It basically said it couldn’t find some required files and threw up a load of standard PHP include errors. After deleting and trying again, the problem disappeared so it appears there was a corrupt download on first attempt. I have amended the review now.

Craig F. 2013-08-15T12:56:00+00:00

Thanks for the feedback. Re: the include errors. The plugin was using dirname(__FILE__) to get the directory folder, but I’ve changed that in 1.0.1 and I’m just committing at the moment. Now that I’ve seen your updated message it may not be necessary but we’ll see what happens. I like your suggestions as well, will definitely look into these in a later update.