WordPress.org
Get WordPress

Plugin Directory

Changeset 988138


Ignore:
Timestamp:
09/12/2014 09:58:27 AM (12 years ago)
Author:
lilmike
Message:

Fixed a critical conflict between inline php and 2mb autocode that could cause your blog to become inaccessible. See instructions on the plugin page for a fix.

Location:
2mb-autocode/trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • 2mb-autocode/trunk/2mb-autocode.php

    r988120 r988138  
    66Plugin Name: 2MB Autocode
    77Plugin URI: http://2mb.solutions/plugins/autocode
    8 Version: 1.1.1
     8Version: 1.1.2
    99License: Gpl v2 or later
    1010*/
    … …  
    115115}
    116116
    117 add_action('the_content', 'do_php', 0);
    118 function do_php($content) {
    119     $content = preg_replace_callback('/\[php\]((.|\n)+)\[\/php\]/', 'exec_php', $content);
     117add_action('the_content', 'twomb_autocode_do_php', 0);
     118function twomb_autocode_do_php($content) {
     119    $content = preg_replace_callback('/\[php\]((.|\n)+)\[\/php\]/', 'twomb_autocode_exec_php', $content);
    120120    return $content;
    121121}
    122122
    123 function exec_php($matches) {
     123function twomb_autocode_exec_php($matches) {
    124124    ob_start();
    125125    eval($matches[1]);

  • 2mb-autocode/trunk/readme.txt

    r988120 r988138  
    55Requires at least: 2.7.0
    66Tested up to: 4.0
    7 Stable tag: 1.1.1
     7Stable tag: 1.1.2
    88License: GPLv2 or later
    99License URI: http://www.gnu.org/licenses/gpl-2.0.html
    … …  
    5252Simply put  ##do_top_home## or ##do_bottom_home## anywhere in the post.
    5353
     54= My blog is broken and just shows the white screen of death after upgrading to 1.1 or 1.1.1! help! =
     55
     56Do not worry, the fix is a simple one:
     57
     581. Delete or move the inline php plugin folder on your server, and the blog should be accessible again.
     591. Now upgrade to 2mb autocode version 1.1.2, which fixes this particular issue.
     601. Optional but highly recommended: Replace all [exec] or <exec> tags with [php] tags to allow 2mb autocode to do the php for you, and you will have no need for inline php.
     61
    5462== Screenshots ==
    5563
    … …  
    5765
    5866== Changelog ==
     67
     68= 1.1.2 =
     69*Very important! If you were using inline php to put php on your blog before, please upgrade to this version or uninstall inline php before upgrading to 2mb autocode 1.1. There was a problem that caused the two plugins to conflict, which has now been solved. *** NOTE *** if your blog is not accessible due to the conflict, do the following: Delete the inline php folder from your server, and all should be well. We're sorry for any inconvenience -- sometimes even plugin developers can screw up ;-).
    5970
    6071= 1.1.1 =
    … …  
    7485== Upgrade Notice ==
    7586
     87= 1.1.2 =
     88If you use inline php to do your php inside posts:
     89
     90*You don't need to anymore, as this plugin will handle it for you.
     91*Please update to this version or uninstall the inline php plugin because the two plugins conflict. This has now been fixed.
     92*If your blog is totally broken and you cannot access the admin panel to remove the plugin inline php, then simply delete the inline php plugin folder from your server, and the problem will be solved. Sorry for any inconvenience (even coding ninjas are durps sometimes too, ;-))
     93
     94= 1.1.1 =
     95If you didn't know how to use the plugin... this update is for you. This update adds documentation inside the plugin, as well as adds ##do_top_home## and ##do_bottom_home## to force displaying the text on a per-post basis on the homepage, no matter what the checkbox says in the options pannel.
     96
    7697= 1.1 =
    7798If you were using php at the top or bottom of a post, please upgrade to this version as this fixes a possibility that the php code would not run or the php may have echoed to the wrong part of the screen. In addition if you want to run php code in your posts without having to add it to every post, then you may like this release. Also, if you wish to turn off the placing of text on a per post basis for the home and/or single post pages, this update is for you.
Note: See TracChangeset for help on using the changeset viewer.