Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • Forum: Installing WordPress
    In reply to: Hashes with */
    Thread Starter saltyp

    (@saltyp)

    Thanks. I wonder if there is some validation step that bitnami has left out because I have seen it more than once.

    That #contact anchor is a dead link.

    I am desperately trying to do the same thing. Just get rid of optimole. I am troubleshooting and I absolutely cannot remove the optimole links from elementor. Even if I go into a page and remove the image and replace it optimole jumps in and changes the link.

    I really do not know what’s going on. I want it gone.

    Thread Starter saltyp

    (@saltyp)

    Thats how I like using it. I build sites just throwing in pictures. Not knowing what ones ill keep. Then at the end I want to rename all the final ones.

    Why can’t you just have it write a bunch of redirects?

    Thread Starter saltyp

    (@saltyp)

    That sucks. I really like the plugin.

    I mean you do say backup like 5 times. I just was shocked when everything was gone on the frontend.

    Thread Starter saltyp

    (@saltyp)

    Ok I got something working but I get an error from the plugin

    “There has been an error. Form has beensubmitted successfully, but some actions might not have been completed.”

    Can I edit this message to just “check your email for verification”

    lol there is a typo in it as well.

    Thread Starter saltyp

    (@saltyp)

    This multisite has 5GB allocated to it. It has many sites.

    Idk. The workaround looks good and works good.

    Thx for the help tho.

    If I ever figure out what it was I will post here.

    This issue has been documented many times over the years. I saw many treads about it. The usual wp fixes never seem to work.

    Idk. Ive been threw every log file I can find and no dice.

    Thread Starter saltyp

    (@saltyp)

    Nope never solved it. Used a work around. As far as I can tell it is woocommerce itself. I tried everything under the sun. The major red flag is that I could go into safe mode with literally only woo commerce activated and the problem persisted.

    I even reinstalled woocommerce to address corrupted files.

    But yes close the thread.

    Thread Starter saltyp

    (@saltyp)

    So there is no way to instruct w3 total cache to not create a new .htaccess all the time?

    Like I said I made a blank .htaccess and set it to read only. It worked to block w3 but the entire site turned into a 404 ecept the homepage that was missing all its css because the w3 cache files failed to load…

    • This reply was modified 3 years, 9 months ago by saltyp.
    Thread Starter saltyp

    (@saltyp)

    Yes I know how to update their htaccess.conf
    The problem is that w3total cache keeps creating a new .htaccess in htdocs. It conflicts with the real one. Apache finds it and cases all types of problems.

    Update. So I created a blank .htaccess in htdocs and set the permissions to root only so w3 could not use it. Well that crashed everything.

    I am at the point of just ditching w3. It dose not let you configure the htaccess location. It just insists on creating rogue files and will not let you configure a different location for the htaccess file as far as I can tell.

    Is there anyway to do this? I like w3, it has many options but this is a critical flaw.

    Thread Starter saltyp

    (@saltyp)

    the .htaccess file created by w3 had incorrect rewrite rules… I am really hoping this was the problem.

    Apparently apache will use whatever .htaccess that is in an active directory. so the w3 rules would have been applied. but also all the incorrect rewrite rules.

    so to me it makes sense that removing the incorrect file would solve my issues.

    but only time will tell.

    Thread Starter saltyp

    (@saltyp)

    I might have made a breakthrough. So the css not loading was because i did not delete the htaccess file that was created in the htdocs folder.

    So i applied the w3total cache changes to the bitnami htaccess.conf. deleted the one made by w3total cache in the htdocs folder. w3total cache detected this. told me to clear the page cache, i did. then the page become visible!

    This very well could have been the issue. i will keep this thread updated. thank you for telling me to dig dee4per into the htaccess file situation.

    I will post if this resolves the issue. there is nothing i hate more then people on these threads not posting the solution to their problem… selfish people.

    Thread Starter saltyp

    (@saltyp)

    Ok so I was just looking into my .htaccess situation. It is funny. the bitnami wordpress stack dose not use the /htdocs/.htaccess file that w3total cache creates. It uses a different one.

    Refer to this page https://docs.bitnami.com/installer/apps/wordpress-multisite/administration/use-htaccess/

    So I followed the instructions and took the w3total cache config lines and placed them in the active htaccess.conf. Well then the site failed to load any CSS and I reverted back to the original file.

    My question is: Is w3total cache working at all? if its htaccess rules are being ignored by apache?

    The active htaccess file looks untouched. and has no w3total cache rules in it.

    For months and months there was never an issue. this is just getting to me know.

    I put the shop page on the do not minify list. it was already on the do not page cache list.

    we will see if that solves the issue. when the css failed to load I updated the permalink structure and the problem went away again so I cannot test any strategies.

    Edit: I left the wp-config file open by accident in nano for weeks lol. could that cause any issues?

    • This reply was modified 3 years, 9 months ago by saltyp.
    Thread Starter saltyp

    (@saltyp)

    Yes I update everything manual. Cleared all cache. Didnt fix it. Ive fixed many problems. This one is big and has me stumped. Im ready to startup an entirely new VM and see if that works.

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