WPIntell

Source evidence

Fatal error: Call to undefined function screen_icon()

Advanced Export for WP & WPMU · support · 2015-10-09T21:45:00+00:00

complaintsentiment
highseverity
1.0relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

5 / 35 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
berkleegrad unresolved
Trying to Migrate an old install (Yes it’s really on WP 2.6) The plugin installs; but, when I click on manage > Advanced Export, I get the following error “Fatal error: Call to undefined function screen_icon() in /usr/…/wp-content/plugins/advanced-export-for-wp-wpmu/ra-export.php on line 260” Is there a work around or an older version of the plugin that would work with WordPress 2.6? My friends are desperate… Thanks in advance, -Rick https://wordpress.org/plugins/advanced-export-for-wp-wpmu/ I wrote the original version of it for WP 2.8. You could comment that line out by adding // to the beginning of the line. Greetings Ron, thank you for your response. Yes, I understand the code is for version 2.8 and yes, my friends are really running 2.6 =:0 Their code has a heavily modified core code install and was told by the coder to NEVER update or it would break everything. They have asked me NOT to update the core code =:o Following your suggestion, I have rem’ed out the line; however, that just starts the error at the next line down and when I remark out the next line, the error proceeds to the next line e.g. “Fatal error: Call to undefined function” . I have not commented out the entire section; but, suspect that if I did that would negate the export function. I do appreciate you taking the time to reply. Thank You, -Rick Did you put the // before or after the <?php (begin PHP code)? If you put it before then the slashes would have had no effect.

Comments

3 shown
Ron Rennick 2015-10-10T01:47:00+00:00

I wrote the original version of it for WP 2.8. You could comment that line out by adding // to the beginning of the line.

berkleegrad 2015-10-10T11:29:00+00:00

Greetings Ron, thank you for your response. Yes, I understand the code is for version 2.8 and yes, my friends are really running 2.6 =:0 Their code has a heavily modified core code install and was told by the coder to NEVER update or it would break everything. They have asked me NOT to update the core code =:o Following your suggestion, I have rem’ed out the line; however, that just starts the error at the next line down and when I remark out the next line, the error proceeds to the next line e.g. “Fatal error: Call to undefined function” . I have not commented out the entire section; but, suspect that if I did that would negate the export function. I do appreciate you taking the time to reply. Thank You, -Rick

Ron Rennick 2015-10-11T01:52:00+00:00

Did you put the // before or after the <?php (begin PHP code)? If you put it before then the slashes would have had no effect.