trex005

That did it! Thank you!

This did not seem to do the trick. I just uploaded the files directly and the version number remained the same. Did I perhaps miss something?

nick, how is it working out for you?

For anyone wondering what happened, the plugin was built on a multisite installation, and apparently administrator was not high enough permission. This is fixed in 0.02

I sure hope wordpress doesn’t show the edit logs, so I can edit that into oblivion when done.

Thanks for calling and sharing.

Of course not. If you are done for the day I understand, however if you’d like I can try to offer you more direct support now. I really would like to know what is going on. Use google, yahoo, msn, facebook or anything we could communicate real time with? Heck I could even let you call me. ??

Can you check to make sure it is indeed active?

I am using 4.3, so it is compatible. The tree should look like this

assets/screenshot-1.png
lib/jquery.lazyload.min.js
readme.txt
theme-catalog.php

argh, I should know better than that! I know many servers can’t handle <?. Boo!

it is working on my server, however that is right after some php open and close tags. maybe your server does not like that. Try replacing this:

?>
<div class="wrap">
	<h2>Theme Catalog Settings</h2>
	<form method="post" action="options.php">
	<?php
		// This prints out all hidden setting fields
		settings_fields($this->static_prefix . "_options");
		do_settings_sections($this->static_prefix . "_options");
		submit_button();
	?>
	</form>
</div>
<?php

With this :

echo '<div class="wrap">
	<h2>Theme Catalog Settings</h2>
	<form method="post" action="options.php">';
		// This prints out all hidden setting fields
		settings_fields($this->static_prefix . "_options");
		do_settings_sections($this->static_prefix . "_options");
		submit_button();
	echo '</form>
</div>';

Your very welcome. You will be my first tester, so let me know of any issues before you ding me! ??

I just uploaded this plugin today, and it is my first plugin. Perhaps the system hasn’t picked it up yet, or perhaps I did something wrong.

You can find the full code in the SVN : https://plugins.svn.www.ads-software.com/theme-catalog/branches/0.01/

Reasons for plain text:

• Easier to verify data accuracy. (Can be helpful when having sending errors)
• Disposable sending account and you lost/forgot the password. (Bad reason, but one nonetheless)

Certainly you want to make it harder to crack, I’m just stating that making it a password field doesn’t really do that for any remotely savvy attacker. To make it (slightly) harder you need to either send an encrypted version (or hashed) to the config page, or a default value. Then on save check to see if that value is altered, and only if it is, update the password.

This clearly won’t protect you from someone who gets access to your database, but it is a good first step. To protect the database, you could encrypt with a seed, but if the attacker was able to find the seed, you’re still out of luck.

Changing it to a password field is not going to stop anyone who is able to hack into your server. Thinking this is any help is misguided.

However, if you insist, the file to change is :
wp_mail_smtp.php line 305