I just installed this extension and I’ve come across this problem

Notice: Uninitialized string offset: 0 in /admin/extensions/ext.publishimprove.php on line 133

Notice: Uninitialized string offset: 0 in /admin/extensions/ext.publishimprove.php on line 204

Notice: Uninitialized string offset: 0 in /admin/extensions/ext.publishimprove.php on line 241

Notice: Uninitialized string offset: 0 in /admin/extensions/ext.publishimprove.php on line 242

Notice: Uninitialized string offset: 0 in /admin/extensions/ext.publishimprove.php on line 243

Notice: Uninitialized string offset: 0 in /admin/extensions/ext.publishimprove.php on line 307

Notice: Uninitialized string offset: 0 in /admin/extensions/ext.publishimprove.php on line 394

Was curious what could cause this since it’s just a notice I’m going to guess that it installed but the script is calling for a empty string. As I’m not the most profienct in php I’m not sure as to how to fix this.

Any clues?

nevermind fixed the problem

Davenport, if the glitch was in the code, please let me know and I’ll include that in my next release. I hope to get a chance to revise it before the end of the month.

TTFN Travis

Yeah it was in the code. The code in itself is fine but it’s asking for input when none has been given. So the Notice shows up until you put in all your settings. Once you set your settings then the Notice disappears. Not a big deal but if someone didn’t realize that they need to put in their settings then it can come off as a shock.

Is this still working in 1.5.2? There are a couple of features that don’t seem to want to “take”, like changing Submit to Save and removing the Quick Save button.

Yes, it’s still working.

Are you logged in as a superadmin? Does it still not work?

TTFN Travis

Yes and yes.

I tried uninstalling and reinstalling too.

1.6.0 - June 26, 2007

• I have integrated the textarea extension into this extension. (See Copyright)
• Fixed a small publish page bug

The bug was that when there was only one weblog, it didn’t replace the text. See the first message to download this version.

* I have integrated the textarea extension into this extension….

WHAT DOES IT MEAN????

If you wish improve or extend functionality of the extension, let me know through forum or PM. I include your suggestion info next version with your credit. But DO NOT include other work under your work without any permission.

I’m very disappointed your steps.

Please, read my PM!!

Hi, Gabriel.

I read your PM and I will be removing the textarea extension functionality as soon as possible.

I did try to contact you several times, and thought your extension was abandoned when I didn’t hear back. I apologize that I went ahead and included it without your permission.

TTFN Travis

Please, respect copyright notes in the extension - the same, you are using as well.

No answer means ‘no’, not ‘yes’.

supersusie: Please, STOP immediately distributing v.1.6 of your extension! I thought, it will be happen after my yesterday’s post. Did you think, I will be wait on your next version or so??? It’s unbelievable, are we living on the same planet?

Gabriel,

Yes, we are living on the same planet, and we should all be a little nicer to each other because of that.

I have a day job, and that means it might take me a day or two to update this extention, which I contribute to the community for free. I contacted you six months ago in this forum and by private email, and when I didn’t hear back after several versions of my extension, I assumed that your version 1.0 extension was abandoned. So I included your extension’s functionality in mine, and put this note in the README:

I do not claim copyright to the part of the code that makes the text areas expandable. That code came from the ext_textarea_resizer: Written by: Gabriel Schwardy Copyright (c) 2006 Caleydon.com http://www.caleydon.com/portfolio/ee/ I made several attempts to contact Gabriel but never got a reply, and will gladly remove his portion of the code if he requests it. However, I thought it was an excellent fit and I hoped he wouldn’t object, given that we both distribute our code for free.

I totally admit that you have every right to expect me to remove your code, and to stop distributing it as soon as is reasonable. But you don’t have to be rude about it. If you look back in this thread, you’ll actually see a comparable situation: another developer took my code and modified it (to fix an incompatibility), and I asked him, privately and politely, to remove his version, and he did, and we’re all still on speaking terms.

So, once again, I’m sorry, and I’ve now modified and reposted my extension as version 1.7, and I hope we can move past this.

TTFN Travis

supersusie: please, enough! Do not distribute version 1.6 with Texarea resizer in the version 1.7! I’m appreciate your work for EE comunity and your activity, but now I’m disappointed more and more.