dw_beta | New Create Entries beta, round two

The next code push will update the new Create Entries page in beta with a number of fixes for previously-reported bugs and enhancements. To make it easier to keep track, we're therefore opening up a new bug-reporting post (to avoid confusing things with bugs reported in the previous post).

When reporting bugs, please include:

* The browser name, browser version number, and operating system you're using
* The steps you took to reproduce the problem
* Whether or not you've tested the same steps in another browser (and if so, which)
* Whether you get the same result every time you try the same steps, or if it only happens sometimes

If we can't reproduce the problem under the same browser and operating system, we may also ask you for a list of any browser extensions you have installed.

Things that are still not yet implemented:

* the "don't autoformat" button
* the rich text editor
* editing existing entries (it will display the old form)
* draft posts of any type, including autosaving of entries

There are also still some issues with IE, especially in "privacy mode". Anything that requires Javascript is currently not working in IE in privacy mode, and we're trying to figure out if there's something we can do to fix that or if the settings of the browser override anything we can do.

Flat | Top-Level Comments Only

I'm honestly not sure if this is related or not. I just tried to post using the beta create entry page for the first time, and also for the first time, I got a crosspost-failed email.

I'm running Windows 7, Firefox 3.6.10
I have not tried in another browser yet (nothing else to post). I will try tomorrow though.
Basically all I did was make a short entry and post it, and then the crosspost failed. I'll include here a copy of the notification email I got, but I don't understand what it means, so I don't know if it's related or not. I will note, though, that crossposting to journalfen failed but to LJ succeeded.

--- email follows ---

Failed to crosspost entry to rainne@JournalFen: Failed to access class (LJ::XMLRPC): Can't locate LJ/XMLRPC.pm in @INC (@INC contains: CODE(0xcaad604) /var/www/vhosts/journalfen.net/lj_jfcustom/cgi-bin CODE(0xcaad334) CODE(0xca9770c) CODE(0xca9743c) CODE(0xca9716c) CODE(0xca96e54) /var/www/vhosts/journalfen.net/lj_jfcustom/src/s2 CODE(0x908bdfc) /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 . /usr/local/apache/ /usr/local/apache/lib/perl) at (eval 1790)[/usr/lib/perl5/site_perl/5.8.8/SOAP/Lite.pm:2727] line 3. --
Dreamwidth Team
Dreamwidth Studios

Hey -- do you get the same error if you have the update beta off? (http://www.dreamwidth.org/betafeatures to turn it off)

JF is running a really really old version of the LJ code, and some things are very broken when trying to interact with them -- that's why we had to disable imports from JF, for instance. That error makes me think it's the same problem, but I just want to rule out the new update page as a possible cause first.

I didn't this morning when I posted using the old page.

*nod* Can you explicitly try turning off the beta and then trying to crosspost again, though? It'll just help us narrow some things down! (I'd do it myself except I've lost the pw to my JF account and I don't have access to that email anymore.)

Interestingly enough, it failed again.

Failed to crosspost entry to rainne@JournalFen: Failed to access class (LJ::XMLRPC): Can't locate LJ/XMLRPC.pm in @INC (@INC contains: CODE(0xcaad604) /var/www/vhosts/journalfen.net/lj_jfcustom/cgi-bin CODE(0xcaad334) CODE(0xca9770c) CODE(0xca9743c) CODE(0xca9716c) CODE(0xca96e54) /var/www/vhosts/journalfen.net/lj_jfcustom/src/s2 CODE(0x908bdfc) /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 . /usr/local/apache/ /usr/local/apache/lib/perl) at (eval 1486)[/usr/lib/perl5/site_perl/5.8.8/SOAP/Lite.pm:2727] line 3.

*wince* okay, yeah, that's probably due to the outdated JF code. I'll have one of our backend gurus look at it to see if there's anything she can do, but I don't know if it's something we'll be able to work around. Sorry :(

I'm not too fussed about it. I'm not a hundred percent sure anyone actually uses journalfen any more. I mostly only have it for backup, and IJ does that just as well. :)

I'm WAY more excited about that little options button that I totally missed before.

YOU CAN MOVE THINGS

AND PUT THEM WHEREVER

although i will admit, I set up my official DW account differently than my personal account, since I use drastically different workflows between the two, and that's breaking my brain a little. *g*

....I'm also kind of giddy and punch-drunk after the day I've had. Perhaps I should go to bed.

I was IN BED and GOT OUT OF IT to check on this for you. XD

(You're welcome!)

okay, that totally deserves cookies

WHICH I AM EATING RIGHT NOW okay they're chips ahoy so they're not *great* but still

...seriously. i'm going to bed now before i make ~~more of~~ a fool of myself

CHIPS AHOY.

OM NOM NOM.

ARE THEY THE CRUNCHY ONES OR THE SOFT ONES. I LIKE THE SOFT ONES BETTER.

XD

Yes, I think I too should return to the land of flannel sheets. My butt's getting cold. XD

Actually, something's just occurred to me. I'm looking at my JF and I'm realizing that nothing I've posted since July of 2010 has crossposted, and I didn't know it. Apparently I wasn't getting the failure notifs. AND when I went and looked, I had the wrong password in. So, um, go figure.

HOWEVER, I fixed the password and then went and tried to crosspost again, and it still failed, and I'm pretty sure it's the same error message, so... um... yeah? *facepalm*

---
Failed to crosspost entry to rainne@JournalFen: Failed to access class (LJ::XMLRPC): Can't locate LJ/XMLRPC.pm in @INC (@INC contains: CODE(0xcaad604) /var/www/vhosts/journalfen.net/lj_jfcustom/cgi-bin CODE(0xcaad334) CODE(0xca9770c) CODE(0xca9743c) CODE(0xca9716c) CODE(0xca96e54) /var/www/vhosts/journalfen.net/lj_jfcustom/src/s2 CODE(0x908bdfc) /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 . /usr/local/apache/ /usr/local/apache/lib/perl) at (eval 1644)[/usr/lib/perl5/site_perl/5.8.8/SOAP/Lite.pm:2727] line 3.

yeah, our backend guru tells me that's almost certainly because of JF's old code. I unfortunately don't think there's anything we can do to fix it -- JF would need to update the code on their end :(

Well, the hell with JF, then! WINE FOR EVERYONE! XD

*goes back to playing with the components*

New Create Entries beta, round two

Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated

Re: Possibly unrelated