Help activiating this

Hi Robert!

Just to be clear, this plugin allows you to take docs into WordPress, not extract from WordPress to InDesign.

I don’t have an InDesign script for this process. Which script are you referring to?

yes I’m aware of that. I’m asking for your help with the docs to word press portion I’ve configured the settings for the plug-in and I’ve created folders on Google drive but nothing happens and I’m sure there’s more that I need to do but frankly it’s not very clear in the installation guide all the steps you need to take to make this work and I was hoping you could help me since you pick up errantly have it working on your Google Docs and your WordPress site.

Okay. If you haven’t already, take a look at this thread:

https://www.ads-software.com/support/topic/error-redirect_uri_mismatch-4?replies=12

About 4 comments up from the bottom, there’s a recap to all the steps we had to do from scratch to install this and get it to run.

Once you’ve confirmed you’ve enabled all the steps, authorizations, and still nothing is happening, try manually running your CRON job*. (Or, this may sound strange, but when the CRON plugin isn’t working, I’ve found if you go to Settings->Docs to WordPress and click on the ‘Save’ button a couple of times it’ll work.)

I’ll usually just create a new doc in the ‘source’ Google Drive folder to test this out. If it works it should disappear out of that folder and be moved to your ‘processed/finished’ Google Drive folder. It’ll also appear as a ‘draft’ post in your WordPress.

You can also modify your CRON script to include a command to email you when it’s run – that way you’ll know it’s working and it’ll tell you what it’s moved over.

$result = $docs_to_wp->startTransfer();
wp_mail( "YOUR_EMAIL_ADDRESS", "Docs To WordPress", print_r( $result, true ) );

See the thread at https://www.ads-software.com/support/topic/10-beta-questionsissues?replies=26 for more information. This thread also includes code I had to remove from my plugin to get it to work with my server, but you may not have to go that far.

*To manually run your CRON job open a new window or tab in your browser and go to https://YOURDOMAIN.com/docs_to_wordpress.php I honestly can’t remember if that PHP file gets installed into your root directory when you install the plugin, or if I had to create it (it’s been too long). If you need to create that file, here’s the code:

<?php
include('./wp-load.php');
$docs_to_wp = new Docs_To_WP();
$result = $docs_to_wp->startTransfer();
wp_mail( "YOUR EMAIL", "YOUR SUBJECT LINE”, print_r( $result, true ) );

Hope this is enough to put you on the right path. Let me know of any error messages you get along the way. It’ll help pinpoint where the problem is.

Good luck.

Working on a video that shows how to install this from scratch. Should hopefully have it posted Monday.

Here is the error I received.

Parse error: syntax error, unexpected ‘@’ in /home/content/p3pnexwpnas09_data03/87/2786987/html/docs_to_wordpress.php on line 5

Then I made this the php file

<?php
include(‘./wp-load.php’);
$docs_to_wp = new Docs_To_WP();
$result = $docs_to_wp->startTransfer();
wp_mail( “YOUR EMAIL”, “YOUR SUBJECT LINE”, print_r( $result, true ) );

And got this error:

Parse error: syntax error, unexpected end of file in /home/content/p3pnexwpnas09_data03/87/2786987/html/docs_to_wordpress.php on line 5

My PHP-fu is highly limited, so I suggest you start a new thread with the subject of “Help with Parse error/Syntax error,”(or something along those lines) just so you can get the right set of eyes on the problem.

I will mention that one of the big issues I was having, that I didn’t even realize was causing a problem, was that I was using two different browsers each logged into a different Google account. When the script would try to run/authenticate, it threw up all sorts of errors because it would be trying to access Google credentials from the wrong account. Slim to none that that’s your problem, but I thought I’d mention just in case.

I’ll have the video up sometime today. Don’t know how much it’ll help at this point, but it couldn’t hurt.

Good luck.

Well I changed the docs_to_wordpress-php file to the following and now all it returns is a blank html page when type lava/media/docs_to_wordpress.php in the browser and hit return

Here is my php text

<?php
include(‘./wp-load.php’);
$docs_to_wp = new Docs_To_WP();
$result = $docs_to_wp->startTransfer();
wp_mail( “YOUR_EMAIL_ADRESS”, “Docs to WordPress”, print_r( $result, true ) );

Ok, to be clear:

You created a PHP file named “docs_to_wordpress.php” and the content of that file is:

<?php
include('./wp-load.php');
$docs_to_wp = new Docs_To_WP();
$result = $docs_to_wp->startTransfer();
wp_mail( "YOUR_EMAIL_ADDRESS", "Docs to WordPress”, print_r( $result, true ) );

You’ve filled in the ‘YOUR_EMAIL_ADDRESS” field with your email. And you placed that file in your root directory (pretty sure it has to be in your root). Then you use your browser to access that file at:

https://yourdomain.com/docs_to_wordpress.php

You get a blank HTML page, correct? That’s what should happen. You should then receive an email with the subject line “Docs to WordPress” and the body of the email should list an array of files that were scooped from your GDrive into WordPress (or, a blank array).

Let me know what that email says.

No, if I put email address in it, this is what I get:

Parse error: syntax error, unexpected ‘@’ in /home/content/p3pnexwpnas09_data03/87/2786987/html/docs_to_wordpress.php on line 5

I only get a blank document when it says “YOUR_EMAIL_ADDRESS”

Stupid question, but did you leave your email contained in quotes?

For example, my line 5 is:

wp_mail( “[email protected]”, “Docs To WordPress PC”, print_r( $result, true ) );

yes

Okay – show me your line 5. It makes no sense that it’s ‘reading’ that @ symbol as a syntax error. It shouldn’t see it.

Also – this whole portion is optional. You only need to do this (create this PHP CRON file and manually run it) if, for some reason, your CRON plugin isn’t working. (My plugin wouldn’t work because I’m running 8 sites, and my host flags it as a malicious attack to have that many CRON inquiries at once).

wp_mail(“[email protected]”, “Docs To WordPress PC”, print_r( $result, true ) );