dentm42
Forum Replies Created
-
Forum: Plugins
In reply to: [Sermon Manager] Jetpack Triggers Error in sermons.php (line 560)It appears that the function it’s choking on is only loaded for admin users.
The function sm_get_screen_ids is in file includes/admin/sm-admin-functions.php which is included from file includes/admin/class-sm-admin.php which is CONDITIONALLY loaded in sermons.php only if the current user is an admin (see sermons.php::118-122.
The proper solution would be to move sm_get_screen_ids to a file that is loaded for all users (perhaps includes/sm-core-functions.php ?).
A temporary fix would be to remove the “if (is_admin()) {” conditional by commenting out line 118 and 122 of sermons.php.
The problem is, I don’t know if there are any OTHER functions that may have this problem (usually with a major refactor, if there’s one, there’s more!) and I have my own projects to work on and maintain, but this is the cause of this particular error message.
Forum: Plugins
In reply to: [Sermon Manager] Jetpack Triggers Error in sermons.php (line 560)Installed the version from dropbox. No change in results. Every 5 minutes (when the sync runs), the log spits out the same error message as before.
Yes, we are on 5.5, Jetpack 8.8.2. We are not running Pro 2.0.5.
Forum: Plugins
In reply to: [Social Media Auto Publish] Facebook Posts not publishing PubliclyFB apparently made some minor modifications with their APP interface. You now have to ACTIVATE the app using the switch at the top of the page on the developers site. I ran into this exact problem yesterday and pulled my hair out trying to find the answer. Once you set the status to LIVE, your posts will start flowing properly.
AWESOME!!!!
First – it’s not a bug or error in your code (although I did find something you’ll want to look at). The fix is easy. Since you use “wp_upload_bits” to save the css files, the site operator of a multisite network needs to make sure that “css” is an acceptable upload file type.
NETWORK DASHBOARD –> SETTINGS –> Network Settings
The parameter: “Upload file types” under “Upload Settings” needs to have “css” added. That’s it! Works like a charm after that.
As I was digging, though, I found you used “add_option” in the cache_css function – looking at the logic, it looks like that should be “update_option”. You may have a reason for not doing that – if so, clue me in.
Thanks!
(BTW- NO, it didn’t take me 5 hours to fix this — I fixed the lawn-mower, and did a bunch of other stuff today besides just looking at this.)
I have to say, I would not have thought to use “wp_upload_bits” for this purpose – but looking at what you did, I think it’s the right way to do it. Thanks for teaching me something in the process!
If you have any idea where to point me… I don’t mind digging into the code a bit (I probably will anyway – but any hints would be great!).
If I figure it out, I’ll post a patch.
Forum: Plugins
In reply to: [Custom Contact Forms] Spam?There (is/was) a cross site scripting vulnerability in Custom Contact Forms. The text you quote is part of the way to exploit it. Not sure how to stop it per se. Also not sure from the tracking whether it’s been fixed or not.
More info: http://plugins.trac.ww.wp.xz.cn/ticket/1520