musicmasteria

The plugin isn’t free so there isn’t a download page for it, sorry. Contact me if you are interested in purchasing the plugin.

For those who are looking for a solution to the problem i had before, I have made a plugin that does exactly what I was asking for.

You can find it here:
https://takeouttactics.com/projects/wordpress/plugins/cron-unsticky-posts/

Enjoy!

So donncha, are you updating the plugin to fix this or are we SOL until wordpress comes out with version 2.9.1?

Update:
V1.4.5 of this plugin is out.

Here is a screenshot of the front-end, ‘Mass Post’ page:
https://i235.photobucket.com/albums/ee299/musicmasteria/masspostv145.png

And here is the back-end, ‘Mass Post Options’ Page:
https://i235.photobucket.com/albums/ee299/musicmasteria/mass-post-v14-backend.png

What has changed?:
– ‘None’ added as a choice in Sub/Dub
– System that controls the titles has been updated
– System that controls the post content has been updated
– Added ability to change max # of posts that can be added at a time, located on the ‘Mass Post Options’ page
– Added ‘Final Tag’ feature – When enabled, ‘[Final]’ will be added to the end of the last episode posts by Mass Post.
– Content type is now a selection box rather than just a checkbox. Ability to have multiple formats to choose from, rather than just 1.
– A few other under-the-hood changes

I thought about that but I don’t know how to “pick up” the project.

kairi084,

Sorry that was just the plugin that I found.I didn’t write it so I’m not sure what’s wrong with it in your setup.

Using the include function takes the entire page wp-login.php and includes it in your page. Obviously, this isn’t what you want.

A quick look around found this:

https://www.wpdesigner.com/2007/07/09/how-to-place-a-login-form-in-the-sidebar/

Which gives this code to you:
https://www.wpdesigner.com/wp-content/files/codes/sidebar_login.txt
(copy the content of it, don’t ‘include()’ this txt file)

Place that code in a php widget or add it to your sidebar.php page.

Hope that helps

Rabble/AButlwer, Captcha can be fixed by adding <?php start_session() ?> to the top of wp-login.php

As for the password strength meter, I haven’t found a fix yet.

Might want to take a look at my fix as well because the plugin has errors out of the box:

https://www.ads-software.com/support/topic/274602?replies=4

NasheedsNow.com, might want to go back and check to make sure you didn’t miss anything.

The problem was that a function was being run but nothing was being output (echo-ed) so the urls were messed up.

Look for more lines that do the same and the plugin should work for you again.

I do wish that the plugin author would work on his/her plugin more though… too bad.

For those looking for this as well, here is what I found:

update_option('sticky_posts', $Array_of_IDs_to_stay_stickied);

The array looks like:

Array
(
    [0] => 1111
    [1] => 1112
    [2] => 1113
)

Where 1111, 1112, & 1113 are the post ID’s of the sticky posts you want to keep.

Not exactly what I was looking for but it will do.

This will return an array will all existing sticky posts ID’s:
get_option('sticky_posts');

Enjoy

It works mattyza! Thanks for the help!

I hope to plugin author fixes this in the next version.

I got the same problem here too. Any ideas?

(Quote what bigdawggi said)

The javascript error is caused by the script not printing the “https://[site-name]/&#8221; part of the url in it’s call for the “common.js?ver=20080318” script file.

<script type=’text/javascript’ src=’wp-admin/js/common.js?ver=20080318′></script>
VS.
<script type=’text/javascript’ src=’https://siteurl.com/wp-admin/js/common.js?ver=20080318′></script&gt;

You can fix this error using my fix here:
https://www.ads-software.com/support/topic/274602

Thanks for looking around for me foxnaren!

I took a look at all of them and GD Broken Report looks the most promising because it adds a custom field to the post if it is broken.

Now I wonder if there is a way to display all posts with a certain custom field. Any ideas?

Turns out at least a major cause of it was WP Super Cache not deleting the expired files correctly so they would built up and hog all the resources.