TXP Manji 2
I have updated TXP Manji in the light of recent changes to Textpattern. This theme will now only work with TXP 4.0.2 due to the use of certain new tags not previously available. If you don’t have 4.0.2 you are advised to upgrade. Do it now whether you use this theme or not. I have tried to maintain the original functionality of TXP Manji but I have also reduced the theme’s reliance on plug-ins.
First to go in a major way is rss_suparchive. The new <txp:if_different> tag sounds a little boring but is actually very powerful. TXP Manji 2 still incorporates monthly and category archives, both with menus, and not a single plug-in in sight.
Also dropped is rss_live_search. It’s a nice plug-in but isn’t really necessary as it doesn’t do anything the standard search doesn’t do and requires it’s own section/page. Having said that I have used a separate search section to keep the front-page as clean as possible.
Other plug-ins to hit the dust are glx_if, ob1_if_section and ob1_title. They simply aren’t required any more as TXP can now do their jobs.
So what remains? Only 4 plug-ins are left and of those only 1 is truly required, if_cookie, which controls the changes in the comment entry form for new or returning visitors.
mkp_version is used in the footer to display your current TXP version and revision numbers. If you aren’t too lazy this could be done manually.
hak_textile_tags is used in the comment entry form to provide visitors with easy textile formatting commands. This could be removed as there is a Textile Help button but removal would reduce the functionality from the original WordPress version.
zem_contact is used on the contact page to provide your visitors with a form mailer to aid contacting you. You could use your own form mailer if you prefer but this one is excellent. Of course your site might not require a form mailer so it can be removed.
None of these 3 plug-ins are necessary but I leave it up to you whether you install and implement them. If you decide not to use them you should remove the appropriate tags in the comments_form form template, footer form template and default page template.
New to TXP Manji 2 is the addition of SmoothScroll. This will enable smooth scrolling on all anchor tags. Try clicking on the Search option in the top menu or the Arrow at the bottom of the page. It also comes into play on the Archive pages. Try clicking an option in the Menu or one of the Back to the menu links. It is javascript so requires that your visitors allow this but if they don’t the anchor tags will behave in the standard fashion as they are coded in the usual way.
Also new to TXP Manji 2 is that it validates to XHTML 1.0 Strict. Now don’t tell me I don’t try hard enough.
There is a demo available.
Comments ( 7 )
First of all I have been asked a couple of questions regarding the plug-ins. No particular problem with that but I do suggest in the installation instructions that users read the “Help” for the plug-ins included as they can be customised and used in different ways and in different situations. So far all the questions I’ve been asked about plug-ins would have been answered by reading the “Help” so PLEASE DO SO.
I’m not to happy with the way images are used for the construction of the pages. I’m not talking about true background images or the little icons, but about the rounded-corner images. In my view placing these inside div tags so that they can be positioned using CSS is just asking for trouble. I shall be putting TXP Rin back on-line and experimenting with this problem.
First comment I have is that in both the archives online at the time of writing, the DTD template file is an empty file.
Also, I’d like to suggest a simpler and less intrusive installation method. Is this really the way all TXP templates install? copy/pate 50 times to replace the default forms, and files is not that flexible. Suggest that the template uses its own “unique” names so that any number of templates can be easily installed. And,since the templates seem to reside in the database, the installer could be an SQL file for really quick installation.
As far as calling the templates something unique, this wouldn’t reduce the copy/pasting task at all.
Somebody is working on an installer at the moment that would first encode the templates into Base64 then inject them straight into the database, similar to the way plug-ins are installed. I’m afraid it’s not something I can work on myself as I ain’t no coder. :) You should remember that TXP is new. Things will come to pass over time.
If you are still having a problem with the DTD send me an email and I will get a copy over to you.
Stu.
I had attempted to install your port of Manji on my site.
You might remember me. I backed out and returned to WordPress.
Well. . . the more I looked at your port, the more I looked
at Textpattern.
I’m trying again. I just am soooo drawn to textpattern. I will have to
learn a different way of saying what I now know how to say, but I really
like textpattern.
I am running into a problem on the comments.
I don’t know that call in textpatern but it goes like this. . .
The remember/forget check box in text pattern.
What’s that called?
The txp:comment_remember call. . .
The Remember box is there, Stu, but the
Forget box never shows up.
I’ve posted the comments code here: http://pastebin.com/390871
Can anyone see if I have done something to hack
that fuction into unworkability?
Here is the test site: http://www.FatherLuke.org/
Oh, and Stu? Your port rocks so much that even after I gave up
I have come back to it. You rule, you crazy maniac.
Okay,
Father Luke
Hello,
I’m new to Textpattern and have just uploaded this theme. However after installing it I can not open the links on the top navigation (archives, links, about, contact). I’ve followed all the given steps from the instructions, and double checked it, but can not find what i’ve done wrong. Do I have to create these links myself?
Putting the cool graphics inside divs? Why not. What is all that about? :)
Hi Root. Well initially I was having a problem with gaps appearing in certain other browsers. I think I’ve pretty much cured that problem with the “universal” block of code at the top of the CSS:-
* {padding: 0; margin: 0; outline: 0;}