Comments for Dmytro Shteflyuk's Home

Comment on CodeColorer by Dmytro Shteflyuk

Dmytro Shteflyuk — Fri, 08 Sep 2017 04:27:21 +0000

In reply to Hans Luijten. The plugin is still alive and receives updates :-)

Comment on CodeColorer by Dmytro Shteflyuk

Dmytro Shteflyuk — Fri, 08 Sep 2017 04:26:27 +0000

In reply to Ben. PHP 7 compatibility issues were fixed in 0.9.10

Comment on CodeColorer by Dmytro Shteflyuk

Dmytro Shteflyuk — Fri, 08 Sep 2017 04:25:21 +0000

In reply to Yoann. Which version of PHP do you use?

Comment on CodeColorer by Yoann

Yoann — Fri, 08 Sep 2017 02:29:33 +0000

Hi,

I am facing this error when I try to use your plugin. The error occurs even when I’am on the “setting” page on the “preview” section.
As you can see, I’m running WordPress locally using Wamp server.

1	Fatal error: Call to private method CodeColorer::performHighlightCodeBlock() from context '' in C:\wamp\www\wordpress\wp-content\plugins\codecolorer\codecolorer-core.php on line 55

Any idea ?

Thnaks

Comment on CodeColorer by Ben

Ben — Wed, 28 Sep 2016 22:04:20 +0000

When will codeColorer work w/ php7.0?

I’m getting this error when using PHP7:

1	preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in wp/wp-content/plugins/codecolorer/codecolorer-core.php on line 49

Comment on CodeColorer by Hans Luijten

Hans Luijten — Thu, 24 Dec 2015 00:58:51 +0000

I’ve used this WordPress plugin for years now and just love it …
Since there have been quite a few changes in WP Core, I was wondering if this plugin will be updated in the near future?
(just curious, if development stopped, then I’d better prepare to switch to another plugin – which I’d hate to do)

Comment on CodeColorer by Pam Van Londen

Pam Van Londen — Mon, 06 Jul 2015 21:51:52 +0000

Where can I update the anchor href for html5 when I specify

Comment on My top 7 RSpec best practices by Ryan Biesemeyer

Ryan Biesemeyer — Tue, 23 Sep 2014 21:49:21 +0000

There is no need to raise an exception in order to get a backtrace; Kernel#caller provides the desired behaviour. Also, it is good practice to use Kernel#warn for warnings (which sends output to $stderr by default), instead of puts-ing out to $stdout where it is inseparable from the output of your specs:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

# figure out where we are being loaded from
if $LOADED_FEATURES.grep(/spec\/spec_helper\.rb$/).any?
warn <<-MSG
===================================================
It looks like spec_helper.rb has been loaded
multiple times. Normalize the require to:

require "spec/spec_helper"

Things like File.join and File.expand_path will
cause it to be loaded multiple times.

Loaded this time from:

#{caller.join("\n ")}
===================================================
MSG
end
end

Comment on sCategory Permalink by Александр

Александр — Fri, 17 Jan 2014 08:28:52 +0000

Здравствуйте. При обновлении до версии 3.8 выдает 404 ошибку и повторная активация плагина не помогает. Что еще можно сделать? Спасибо

Comment on Advanced Capistrano usage by Bash

Bash — Wed, 10 Jul 2013 20:55:15 +0000

Thank you very much for item #5 – generating server lists on the fly. This was a huge help to me!

The only change I needed to make was to add :web role node creation inside the loop that already creates :app nodes.