simplistik

No, but I’ll do that now.

I didn’t have any intentions of adding it as a plugin.

I’m actually using Parsedown https://parsedown.org/ to do all the heavy markdown lifting (seems to be the most consistent one). So the implementation of it is very simple: https://gist.github.com/simplistik/7901838

I’ve cut out everything that wasn’t necessary, but that is literally how the implementation is happening, and obviously the include path is subject to the user’s directory structure.

Thanks for the fast response. I get what you’re sayin about the speed issue completely understandable. The solution you provided actually works, for some reason it never crossed my mind that the to do a search within the text.

For anyone else looking for a similar solution this is the concept being used:

add_filter('tablepress_cell_content',  'process_markdown');

function process_markdown($text)
{
    if ( in_array($text, array('#colspan#', '#rowspan#', '#span#')) ) return $text;

    $markdown = markdown($text);

    return $markdown;
}

More than likely means it’s hard coded into the page theme and isn’t dynamically sync’d with the value in ACF.

Disable all your plugins and activate a default theme and see if you’re still not able to upload images.

https://codex.www.ads-software.com/Plugin_API/Action_Reference/login_form

Does it work when you activate a default theme without any plugins activated? I’d try that first and then work from there. If it works then I’d activate your theme, see if it’s the theme that causing the error, still with no plugins active. And if that works, then start activating plugins and see which one is hosing your stuff.

define('WP_DEBUG_DISPLAY', true);

I agree. But the concept in it’s rawest form is just to assign email addresses associated to your own website, that will never be used to each user :).

So you have your own site right, let say the name of your site is “mysite.com” well since you control the email addresses associated w/ “mysite.com” you should be able to just randomly create an email address that you’d never actually create on your server so something like [email protected] would never be an actual email address.

just give them arbitrary emails. since emails aren’t important for your setup it shouldn’t matter if they’re gibberish.

Fortunately anything that calls from the options table isn’t dependent on the id, so you can actually “dump” your options table and recreate it. I put together this relatively easy workflow for my company to fix the inflated increment.

1. Save your DB. Personally, you can just save the wp_options (or whatever you’ve prefixed it with).
2. Completely Optional: I recommend just removing any transient data from the DB, since it’s all temporary and won’t affect your site, you can do that by running this MySQL query:

DELETE FROM wp_options WHERE option_name LIKE '%transient%';

3. Run this MySQL query which will re-increment your table:

SET @count = 0;
UPDATE wp_options SET option_id = @count:= @count + 1;

4. Reset the options increment, run this MySQL query:

ALTER TABLE wp_options AUTO_INCREMENT = 1;

Note: wp_options might (should) change depending on what you’ve prefixed your tables with.

Good job man, thanks for the timely response ??

That’s not the solution people are looking for racastro. It’s not an issue of displaying the image on the front-end, it’s an issue of when you press “Set featured issue” on the back-end it doesn’t allow you to select your image out of the NextGEN gallery.

style-light.css and page.css are stylesheets … not pages.

#eee is getting overridden by the background image sprite, the position of the sprite is what is affecting the color of the navigation.