DanClarkePro
Forum Replies Created
-
Forum: Plugins
In reply to: [ShareThis: Free Sharing Buttons and Tools] Broken Short URLSame problem here:
"Winter Portfolio https://shar.es/Y4upD via @sharethis"
That should link to https://www.attitudedesign.co.uk/2013/winter-portfolio/ but it’s linking to https://www.freebooksource.com/?p=59152
Obviously this is a big problem as you think you’re sharing a link with your followers (in some case thousands) and it turns out it is going to the wrong website, not even related to the website it came from.
I have a feeling this might(?) be to do with the URL that the plugin provides, for example:
st_url="/2013/winter-portfolio/"
I think this should be the full URL.. that might fix the issue.Again, as the OP says this is also happening on our LIVE site: https://www.attitudedesign.co.uk/2013/winter-portfolio/
I look forward to responses.
Thanks Sed for these changes, just activated the new version of the plugin and all is well.
Thanks again,
Dan.
This also affects the searching for new plugins – the star rating system:
div.star-holder { position: relative; height: 19px; width: 100px; font-size: 19px; }
It looks like this: https://cl.ly/MFxi
It should look like this: https://cl.ly/MFm5As you can see from the error, it is caused in more_fields, not more_types (although they are closely related)
To fix it change, I would go into the referenced file in your post and change lines 287-289 from:
do_action('mf_box_head', $box); foreach ((array) $box['fields'] as $field) {
to:
do_action('mf_box_head', $box); if(!is_array($box['fields'])) { $box['fields'] = array(); } foreach ((array) $box['fields'] as $field) {
(Add the extra line into the gap between them)
Hope this helps,
-Dan.
This was fixed, if anyone has this problem it was caused by Advanced Category Excluder. Seems some extra categories became selected after update.
Thanks.
Forum: Plugins
In reply to: [More Fields] WYSIWYG field broken in WordPress 3.2Sorry, WordPress took it’s time to tell me there was an update, however the error for me wasn’t in more fields, it was in more types.
The file more-types-settings-object.php on line 29
wp_enqueue_script('tiny_mce');
was commented out, after uncommenting, it worked.Note: this was only affecting user level “Editor”, it was fine for the admins..
Forum: Plugins
In reply to: [More Fields] WYSIWYG field broken in WordPress 3.2I cannot see this on line 81 of more-fields-settings-object.php.
Is there anything else that I could try?Disabling More types or More Fields brings the visual editor back into play, but it seems there is nothing I can try which will make it work when both are enabled.
I look forward to your reply.
You could also say that if it is empty, make it an empty array. Because if it is not empty then it will be an array anyway.
if(empty($mytax)) { $mytax = array(); }
What’s the URL that is returned? (If you’re still having this issue)
Forum: Fixing WordPress
In reply to: SQL attack on wpress 2.9.2Guys, you might want to look at this post:
https://mby.me/JHin short:
configuration files should only be read by Apache, but some users (well, lots of users) left it in a way that anyone could read it (755 instead of 750 in Linux slang).A malicious user at Network Solutions creates a script to find those configuration files that were incorrectly configured.
This same malicious user finds hundreds of configuration files with the incorrect permissions and retrieves the database credentials
Working on changing the permissions now..currently can’t change them as I am not root, emailing NS now.
Forum: Fixing WordPress
In reply to: SQL attack on wpress 2.9.2Did the fix above, fixed mine, will speak to Network Solutions in the morning, odd how only one of my wordpress installations was hit, even though there were another 4 in the same directory, and same account on Network Solutions.
Is anyone having this problem, who isn’t on Network Solutions? As this also happened to a client of mine, I am trying to narrow down what is the cause.
We have changed SQL passwords, login passwords, main password and FTP passwords, but still not sure what caused it!