ajd777

The code should be:

<h2><a href="<?php the_permalink() ?>" <?php do_action('awp_title'); ?> rel="bookmark"><?php the_title(); ?></a></h2>

I forgot a semicolon on the line just before it: ob_end_clean() should be ob_end_clean();

1) do_action (‘awp_title’); is for when you want your title to be used as the show/hide link. You want to use do_action (‘awp_post’);

2) I heavily suggest not using awp_post as it has become an after-thought in the coding process.

3) Do you have an example page you can post where the link is being displayed?

I checked your website and it is a completely different error now, and I think happened while you were editing it. Rather than trying to find exactly what is causing it, I added the updated the SVN so you can download the updated core.js.php file.

I goofed when I copied and pasted. I updated the edit. Basically, you should only have to remove one of the }’s.

There is a second edit that will need to be made if you decide later to use the comment form.:

open /modules/commentform/commentform.php
Find: aWP.doit({'id': _d[i].id, 'type': 'comments', 'force': 1, 'focus': 'comment-'+_d[i].mrc});
Replace With: aWP.doit({'id': _d[i].id, 'type': 'comments', 'force': 1, 'focus': 'comment-'+_d[i].mrc});}

I found the problem. See the fix below.

Open: /js/core.js.php
Find: `switch(_d[i].type){
<?php do_action(‘awp_ajax_complete’);?>
}`
Replace With:`switch(_d[i].type){
<?php do_action(‘awp_ajax_complete’);?>`

Ignore the above post.

I’m not ready to release a new version yet, but I uploaded a new module which should allow you to paginate pages better than that little hack. You can download the new module. I also had to update the Inline Posts Module which allows it to work smoother. If you use the module, you should download this also.

There aren’t any detailed instructions, but I’m now using it on the aWP changelog.

If it really is a jQuery problem, if you are using WP version 2.2+ jQuery is automatically included with your WordPress install, and aWP is built based on it. (If you aren’t, I suggest you upgrade.) If you are using WordPress 2.1, and jQuery isn’t found, it defaults to the sack library.

As for the effect on my homepage: all that requires is going to aWP Management > Posts > “Select simple posts” and set a split mode and a word or paragraph count. There is a readme, but it is still a work-in progress.

Just to clarify, You want this done on a page and not a post?

If so, by default, aWP ignores pages completely because it tends to conflict with some other plugins; however, you may change this behavior by directly editing the code.

Open: /modules/inlineposts.php
Find: is_page() ||
Replace With: (is_page() && strpos($content, '<!--nextpage-->') == false) ||
Find: $count == 2 || $aWP[options]['inlinepaginatedposts'] != 'Enabled'
Replace With: !is_page() && ($count == 2 || $aWP[options]['inlinepaginatedposts'] != 'Enabled')

I haven’t tested the above code, so let me know if it doesn’t work. I’ll work a cleaner version into the next release (probably in a couple weeks.)

EDIT:

Also, custom titles are fairly easy. Right after the <!--nextpage> tag just add <!--title=A Custom title-->.

For the second issue disable the aWP cache module: it seems there might be an error in it. If the cache module isn’t working correctly, it is possible that the comments are also affected.

If disabling the cache doesn’t solve the first issue, can you post me a link to where I can download the theme?

What version of PHP are you using to get this warning?

Unfortunately, the ampersands must remain to ensure PHP 4 compatibility.

https://anthologyoi.com/wordpress/plugins/wordpress-dashboard-editor.html
It can remove the Development blog

Yes it is. If the user (or bot) doesn’t have javascript enabled the link functions just as a normal link to the post/comments/add comments.

Protected directories? Do you mean you set a password in htaccess or in Cpanel to certain directories?

No, they use completely different authentication systems.

Open up your themes style.css and find the line that is like ‘body {‘ after that look for the line like: ‘background #FFF;’. Change the FFF to some other color. Some hex color codes here

Or if you decide you want an image add:
background-image: url(yourpictureurl here);

“So roughly 90% of the viewers of a Kubrick themed site see no bullets.”

Most definitely not 90%, but just because IE is the greatest common denominator shouldn’t mean we use crappy code just to make it happy.

It is the responsibility of the browser itself to make code work,because the only job of the browser is to take text files and make them look pretty. If the browser is deficient it is up to the people that make the browser to make it better; it is not up to the people who make the language.

It is like blaming the company for when your order is lost in the mail when the post office is the one who lost it.