CAC2.0.0 WP3.6 New Activation Errors

[emcniece]

Installed CAC 2.0.0 nightly with the three v0.1 addons in a fresh WP3.6 site - installation is smooth, operation is not. Presented here with the following repeating errors:

Warning: include_once(/home/site/public_html/site.com/wp-content/plugins/codepress-admin-columns-master/classes/column/link) [function.include-once]: failed to open stream: Success in /home/site/public_html/site.com/wp-content/plugins/codepress-admin-columns-master/classes/storage_model.php on line 331

Warning: include_once() [function.include]: Failed opening '/home/site/public_html/site.com/wp-content/plugins/codepress-admin-columns-master/classes/column/link' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/site/public_html/site.com/wp-content/plugins/codepress-admin-columns-master/classes/storage_model.php on line 331

Screenshot:

Not sure if this is a plugin conflict or not yet.

[tobiasschutter]

Thanks, I will have a look.

On 5 augustus 2013 19:28, Eric McNiece notifications@github.com wrote:

Installed CAC 2.0.0 with the three v0.1 addons in a fresh WP3.6 site -
installation is smooth, operation is not. Presented here with the following
repeating errors:

Warning: include_once(/home/site/public_html/
site.com/wp-content/plugins/codepress-admin-columns-master/classes/column/link)
[function.include-once]: failed to open stream: Success in
/home/site/public_html/
site.com/wp-content/plugins/codepress-admin-columns-master/classes/storage_model.phpon line 331

Warning: include_once() [function.include]: Failed opening
'/home/site/public_html/
site.com/wp-content/plugins/codepress-admin-columns-master/classes/column/link'
for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in
/home/site/public_html/
site.com/wp-content/plugins/codepress-admin-columns-master/classes/storage_model.phpon line 331

Screenshot:

[image: CAC WP3.6 Error]https://github-camo.global.ssl.fastly.net/4dee642439feae06bceaae7595258558dcfa39fb/687474703a2f2f692e696d6775722e636f6d2f5859376b4477642e706e67

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9
.

[tobiasschutter]

Did v2.0.1 fix it?

[emcniece]

It seems that the update did indeed fix the issue! Great work, thanks :)