Forum Replies Created

Viewing 15 replies - 1 through 15 (of 123 total)
  • It looks like that url is broken.

    @yordansoares there are a couple of issues to unpack here. First, I don’t know how changing the file extensions will impact the plugin. I think that it might also be possible to over-ride the Glotpress plugin to support the phtml file extension, but I’d need to look. Second, as for the missing __() and _e() – that is something that the developer would need to fix.

    I would encourage you to head over to the github repo here – https://github.com/WP2Static/wp2static and submit a Pull Request and/or an issue, containing the changes that you made. I don’t know if the roadmap for v7 includes better support fo internationalization, hopefully it will.

    I was setting up a new website to use cloudflare and had the same issue.

    output of console log:

    http://staging.atl2018.com/wordpress/wp-admin/admin-ajax.php?action=cloudflare_proxy&proxyURL=zones&proxyURLType=CLIENT Failed to load resource: the server responded with a status of 500 (Internal Server Error)
    compiled.js:34 Uncaught TypeError: Cannot read property 'body' of undefined
        at o (compiled.js:34)
        at Object.callback (compiled.js:29)
        at compiled.js:4
        at d.callback (compiled.js:5)
        at d.<anonymous> (compiled.js:5)
        at d.r.emit (compiled.js:5)
        at XMLHttpRequest.n.onreadystatechange (compiled.js:5)

    I looked at the apache logs, and in fact see some issues:

    [Fri Feb 17 08:12:50.587987 2017] [:error] [pid 7988] [client 70.211.9.141:7133] PHP Fatal error:  Uncaught Guzzle\\Common\\Exception\\RuntimeException: The PHP cURL extension must be installed to use Guzzle. in /var/www/vhosts/staging.atl2018.com/releases/20170217072748/content/plugins/cloudflare/vendor/guzzle/guzzle/src/Guzzle/Http/Client.php:72\nStack trace:\n#0 /var/www/vhosts/staging.atl2018.com/releases/20170217072748/content/plugins/cloudflare/vendor/cloudflare/cloudflare-plugin-backend/src/API/AbstractAPIClient.php(38): Guzzle\\Http\\Client->__construct('https://api.clo...')\n#1 /var/www/vhosts/staging.atl2018.com/releases/20170217072748/content/plugins/cloudflare/src/WordPress/ClientActions.php(41): CF\\API\\AbstractAPIClient->callAPI(Object(CF\\API\\Request))\n#2 /var/www/vhosts/staging.atl2018.com/releases/20170217072748/content/plugins/cloudflare/vendor/cloudflare/cloudflare-plugin-backend/src/Router/DefaultRestAPIRouter.php(62): CF\\WordPress\\ClientActions->returnWordPressDomain()\n#3 /var/www/vhosts/staging.atl2018.com/releases/20170217072748/content/plugins/cloudflare/vendor/cloudflare/cloudflare-plugin-ba in /var/www/vhosts/staging.atl2018.com/releases/20170217072748/content/plugins/cloudflare/vendor/guzzle/guzzle/src/Guzzle/Http/Client.php on line 72, referer: http://staging.atl2018.com/wordpress/wp-admin/options-general.php?page=cloudflare
    

    In my case, not having curl is kind of a ‘duh’ moment. Posting in case it is helpful to others.

    @abcdiamond, I doubt it. this is a very old plugin that is probably not supported or in active development any longer. It might be easy to add though, if you really want it.

    @lucicx I wouldn’t expect for this to work any longer, or for ti to get updated. this is an old plugin that @nacin probably wrote in a couple of minutes, released and hasn’t looked at in a long time.

    I suggest you consider an alternative approach at this time.

    cheers

    similar issue, any response from plugin author?

    Thread Starter rfair404

    (@rfair404)

    Naomi, the issue was partially related to step 6 as indicated by the others. The problem was that the field for the “total” that I had initially used had been deleted.

    It may be helpful if there was some type of notice that “you don’t have a valid mailchimp feed configured” or prevent output of the credit card form in situations where the form feeds aren’t set up correctly.

    two things. First of all is your blog on wordpress.com? if so you may want to try wordpress.com/wp-admin instead of the .org that you listed. Confusing, I know, sorry.

    If that doesn’t work, what is your website address? can you try yoursite.com/wp-admin

    Thread Starter rfair404

    (@rfair404)

    Yes so far that’s the closest one that I’ve found (I’ve done pretty extensive research). The UI is pretty lousy IMHO. I guess it’s time to get to writing another plugin.

    Is there anything inherently wrong with the post-indexer / wp-mu-sitewide-tags approach to creating a “sitewide” table?

    I started working on this today because I needed a quick fix. https://github.com/rfair404/Network-Posts-Widget – It isn’t done yet (obviously) but it is a start. Still welcome alternatives and suggestions.

    Thread Starter rfair404

    (@rfair404)

    I need a widget that displays N latest posts from across the network. Title, excerpt, ftd image etc.

    Oh and a not terrible admin settings page would be nice. WP 3.9.1 compatible.

    It looks like the vhost config is the issue. The error page you initially posted claims that the doc root is /Applications/MAMP/htdocs – looks like you need to find where the localhost directive is specified and set the document root correctly to /Applications/MAMP/htdocs/inserts_local

    if you’re on mac, MAMP sometimes can’t reach the db server on localhost. Can you use the mysql command line to access it this way? e g:

    mysql -u dbusername -p -h localhost

    if not try to usie 127.0.0.1 as db host.

    is the Document root /Applications/MAMP/htdocs indeed where the WP isntall lives – your post leads me to believe that it might not be.

    post a copy of your .htaccess file too.

    Forum: Localhost Installs
    In reply to: Varnish Issue

    it looks like php isn’t working right. Are the file permissions set with –execute ? You might want to post your varnish config .vcl file too.

    If you want your question answered I suggest that you post the question directly instead of linking to another forum.

Viewing 15 replies - 1 through 15 (of 123 total)