Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • edit your robots.txt file takes about 24 hours but this worked for us.

    User-agent: *
    Disallow: /wp-admin

    User-agent: Amazonbot # Amazon’s user agent
    Disallow: /calendar/ # disallow this directory

    User-agent: * # any robot
    Disallow: /calendar/ # disallow this directory

    User-agent: meta-externalagent
    Disallow: /calendar/ # Disallow a specific directory

    you may need to tweak the disallow rules specific to your situation but this immediately solved our issue with the bots rather than blocking it out right which would still consume bandwidth and logs.

    Thread Starter Tech01

    (@htdnet)

    We’ve discussed this with our customer and decided against pushing forward at this time. We will process some other upgrades and continue to work on this portion in the background. Previous designer apparently did not design with upgrades in mind obviously with it being several years old. There is A LOT of custom code not only dealing with the dashboard of WP but also I am guessing with your plugin. After the test upgrade we no longer had access to see the newsletter (old gear icon) in the dashboard under the customer logins nor the new one, said permission denied. When logged in as the admin user, I do not believe the lists migrated over with our last tests but I’ll have to check again. The big thing is the lists of each of the sub-customers need to stay intact. 500+ some users would cause some chaos to manually include them back in the new version? Thanks for your reply Stefano

    Thread Starter Tech01

    (@htdnet)

    Directory permission issues finally resolved…

    I found while the web server was able to update the wp installation the user was not from the website. Required deleting the wp-content\upgrade folder which was recreated on initiating an update to your plugin which then failed again.

    SSHed to the plugin directory and issued the following command to copy all the permissions from the upgrade directory to all plugin folders.

    chmod –reference ../upgrade *

    While visually there were no apparent changes there was somewhere along the line. Leave it up to my panel to cause unknowns.

    Thread Starter Tech01

    (@htdnet)

    it was checked, I unchecked it and tested, no joy, added back again still no go.

Viewing 4 replies - 1 through 4 (of 4 total)