carthik

https://carthik.net/wpplugins/registered_only_patched.phps

is the patched file, for your convenience.

Please let me know if it works fine.

I have to dedicate some time to updating the plugin, but was sort of waiting for 1.5.1. Sorry for the delay.

index.php?page_id=<your-page-id> will also work, without the rewriterules.

Either allow WordPress to write to the .htaccess file by changing permissions of the file, or update the rewrite rules in the .htaccess file manually by editing it. Update the permalinks on Options-> Permalinks to get the new rewrite rules.

Please state where you are at, and what exactly you want to do, in as sepcific terms as possible. It would help others who want to help you to guage what sort of help you need ??

This is a strange problem. I tried helping at #wordpress. New files don’t help. Nothing seems to be wrong with php or mysql.
There are instances of php running out of 8 MB of memory.

get_settings(); doesnt seem to be working, since a lot of variables are not set. functions.php is in fine shape though.

The system is a debian machine.

If someone has experienced these problems, and has a solution, please help.

Yes, if you do not already have a .htaccess file, you have to upload a new blank .htaccess file.

You can set the permissions for the .htaccess file so that WP can write to it automatically, which will save you the trouble of manually editing the file.

Try permissions 600, 644, 666, 777 in that order. The last two are not too secure, just so you know. I personally like to change to 777, let WP do it’s updating, and then switch back to 644. That’s easy and it works ??


<?php $myposts =

get_posts('numberposts=5');

foreach ($myposts as $mypost) :

start_wp();

?>

<li><?php the_excerpt(); ?></li>

<?php endforeach; ?>

Should work in the sidebar, after you do what Kaf suggested above.

Uploads using PHP may be vulnerable. A nitwit could upload a script to delete things, or do wicked things. Which is why WP tries to limit upload to one single directory.

I would suggest you try a File Upload utility. there are many open source tools already that you can search and find.

Why reinvent the wheel ? ??

I can offer some clues. I am sorry I can’t try it out and tell you what absolutely works.

Use the function query_posts (use https://www.cenamayo.com/wpxref to see how the function is written)

Create a new query, something like
$my_posts = query_posts();
Then copy the loop over from the main loop, changing references to $posts with $my_posts , as needed.

You can wrap it in another function is_home();

You’ll hopefully find
https://codex.www.ads-software.com/Conditional_Tags

to be very useful ??

Create a new file on the server, and rename it .htaccess. That is how you can have a .htaccess on your server.

If you use a windows computer, create a blank file on your desktop called 1.htaccess (or myhtaccess.htaccess – the name does not matter). Upload this to the server.

After you have uploaded it, change the name (“Rename” the file) by right clicking on it in your FTP tool, and choosing the “Rename” option. The new name for the file shouldbe .htaccess

I hope that helps, if it’s what you were looking for.

Try $myposts = query_posts(‘cat=1’);

and

foreach ($myposts as $post) : start_wp();

Might work. User https://www.cenamayo.com/wpxref which sort of auto-documents the source.

Ping once manually. The results page will have a link that you can bookmark, or use to ping again, without manually filling things up.

Install WordPress as you normally would, as a fresh blog.
Visit https://example.com/wp-admin/import-mt.php (Using your browser. Replace example.com with your new WP blog’s domain name).

It should be hunky-dory from there on. If not https://blog.carthik.net/index.php?s=movabletype should lead you to an article I wrote about how to move from MT to WP. You have already exported the entries from MT, so that saves you a little work.

Good luck.

Thank you! It is heartening to hear that you liked the way it went. It will only get better.

The strange characters are a result of iso-8859-1 and UTF-8 problems. My guess is that your MT blog used the former and the WP blog uses the latter character encoding.

The most recent comments problem is strange, though.