dbachen

Check this thread for the latest version that works:
https://www.ads-software.com/support/topic/41246

Just a followup since I’m able to reproduce this, I was wondering how to actually log it as a bug for the developers?

Another interesting tidbit. If I offset the client posting time by 4 hours (in the future), then the entry appears to have the correct time under write->manage, but the post doesn’t show up. I guess in the background it’s still thinking it’s 4 hours in the future.

Simply clicking the edit time stamp box, and then doing *nothing* but saving the post again makes it appear. So there is something with the display of the post’s time and the actually publishing time thats a bit wonky.

Are you getting tired of my entries yet? ?? Just wanting to keep you up to date. After recreating the journal, it’s pseudo working.

Synch does not work by itself. It only works when you try and synch excerpts.

Now, I notice when you go back and edit the message after you post it, you can see the custom fields in WP.

In the case where *only* “journal to post to <default>” was selected, the custom field “unt_lj_excerptonly” said it was checked.

In the case where *only* “synch excerpt only” was selected, the custome field “unt_lj_synch” said it was checked.

Those look backwards to me. I think someone else mentioned the sync problem before, but hopefully this information will help you debug.

FWIW, while I couldn’t edit a journal, I tried adding one. Thinking this might give me two journals.. one with the right password, one with the wrong password. Instead, it created a new single journal which overwrote the original settings — in essence fixing the problem with password, but obviously preventing the ability to have more than one journal available to the user.
-D

Arrggg…

Now, the errors don’t appear on the top of the write page, they appear on the bottom..

Here are the first two:
Warning: array_values(): The argument should be an array in /home/dbachen/public_html/chaos/wp-content/plugins/LivePress_1.5.2/LivePress/lpextras.php on line 113

Warning: reset(): Passed variable is not an array or object in /home/dbachen/public_html/chaos/wp-content/plugins/LivePress_1.5.2/LivePress/lpextras.php on line 7

I think that I may have typed my password in incorrectly for LJ. unfortunately, when I try and edit the journal settings, I get a 404 error:
The requested URL /chaos/wp-content/plugins/LivePress_1.5.2/LivePress/lpeditjournal.php&allowlist=dbachen&journal=weezeld was not found on this server.

So while the URL worked to create the journal, it doesn’t call the same location to edit it.

And since you can’t delete the journal, I can’t start it over again. I’m going to try and manually adjust that URL and get it to the right location.

Nope.. trying to manually alter the url and pass the path as: https://www.greenhead.com/chaos/wp-content/plugins/LivePress_1.5.2/LivePress/lpeditjournal.php&allowlist=dbachen&journal=weezeld

if you try and go straight to the lpeditjournal.php file without passing the user and allowed parameters, it generates the following errors:
Warning: main(): open_basedir restriction in effect. File(../../../../wp-config.php) is not within the allowed path(s): (/home/dbachen:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/dbachen/public_html/chaos/wp-content/plugins/LivePress_1.5.2/LivePress/lpeditjournal.php on line 109

Warning: main(../../../../wp-config.php): failed to open stream: Operation not permitted in /home/dbachen/public_html/chaos/wp-content/plugins/LivePress_1.5.2/LivePress/lpeditjournal.php on line 109

Fatal error: main(): Failed opening required ‘../../../../wp-config.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/dbachen/public_html/chaos/wp-content/plugins/LivePress_1.5.2/LivePress/lpeditjournal.php on line 109

I’m really trying to be helpful here, I can imagine the struggles others have gone through as well. I don’t know enough about PHP to fix these things myself.
-D

Sure–

Here’s the first error:
Fatal error: Call to undefined function: __() in /home/dbachen/public_html/chaos/wp-admin/admin-functions.php on line 911

Then it displays the error from WP about not connecting to the database, and then this error:

Fatal error: Call to a member function on a non-object in /home/dbachen/public_html/chaos/wp-content/plugins/LivePress/lpeditjournal.php on line 113

Now, that’s the directory structure of the installation, which is reached at https://www.greenhead.com/chaos

It looks like part of the problem is that I was trying to change the locations of those files, and the name of the folder, rather than putting the entire thing as you named it into the folder.

So, now that my directory structure looks like:
/wp-content/plugins/LivePress_1.5.2/LivePress

It seems to be working. At the very least, I’m able to add the journal settings and begin writing a post without generating errors.

Thanks.

Still no luck. The md5 file is found now, but I still had to manually edit the paths to the other includes, as well as change the url for the lpeditjournal popup.

That aside, the lpeditjournal still does not render properly. After displaying the 3 test boxes, it looks like your code is trying to retrieve the users and then display a save button. That never happens. It craps out trying to load the users with an error. Its generating the error out of admin_functions, line 911, but it seems to be your calling function which is generating the error.

Yup 1.5.2 is up which fixes the problem with the extra headers. However, what it doesn’t fix is the problem with the “add journal”.

What’s probably happening is that the developer already has those entries in their DB and isn’t testing this on a new installation.

From what I can determine so far,
Here’s problem #1:
1) The add journal link should be calling the “lpeditjournal.php” file. This will allow you to setup your journal parameters, like its name and password.

In the older version of LivePress this was stored in a seperate config file, now it’s being stored in the DB.

Without these values, when you try and write a message, you get errors. Why? Because it’s trying to connect to LJ to pull down information, and it can’t connect because it doesn’t know how — the journal isn’t setup.

#2
Now, I tried calling the editjournal file manually, but the php is having errors when it tries using ABSPATH to determine the paths to items such as the md5.js. What I wound up doing was hardcoding mine to point to the actual files with the full path, as the ABSPATH call doesn’t appear to be getting the correct location.

At this point, I’m actually seeing the 3 text boxes to allow me to configure the journal, BUT I’m getting a WP error as it tries to connect to the DB. Says that it can’t, or that the password in the wp_config is incorrect. If it was, WP wouldn’t be working otherwise.

I’m guessing if you can manually make the required entries into the DB you can at least get past this step. I’m trying to trace the PHP now and figure out what it’s doing and why its failing… but at least it’s closer to working.

One problem with the 1.5.1.3 release is that there is plugin header information in every php file. This, in turn, causes each of them to be displayed as being able to be “activated”, from the plugin page. Someone else mentioned this on another thread, but I didn’t see it here. I cut the header information out of each of them, and just left it in the php file in the plugin root. I’m getting the errors displayed when I go to post, I’ll try to back rev the XLMRPC file.