Forum Replies Created

Viewing 15 replies - 241 through 255 (of 3,259 total)
  • Cooee,

    There are plugins that let you host a video on say youtube and embed the video player in a page or post. One of the benefits of this is that you do not have to carry the video bandwidth in your hosting.

    Firstly please add FSFW (Not Suitable for Work) to title.

    Your CSS can specifically target just this tickbox by using the class specifier like:
    .wc-gzd-checkbox-placeholder-legal
    But sorry, I can’t figure out how to color the tick.

    Most likely the problem is that your WordPress Address and Site Address are invalid in the context of your “another computer”.
    The sever is successfully delivering the website page, however the server uses the WordPress Address and Site Address to embed in the page the network addresses of the CSS and script files etc that support the page. On your “another computer” use your browser inspector to see how the CSS and script files are described, most likely they are in terms of “localhost”, from that computer it does not map back to the IP address of your server.
    Solutions include:
    – Set your WordPress Address and Site Address to the IP address of the server.
    – Use the VirtualHost method to configure the website to use a name, then use the “hosts” file to map the name to the server, more details here:
    https://httpd.apache.org/docs/current/vhosts/name-based.html
    https://en.wikipedia.org/wiki/Hosts_(file)

    Suggest that you review the apache error logs, located /var/log/apache2
    Have you enabled debugging ? in WP as well as apache server.
    As well as owned by www-data the directory also needs to be writable by them.

    Finally it may not be necessary to be able to use the website upload abilities to develop and run WordPress, you have shell and GUI file browser access to the files, it is only recently that I have configured my development sites to use www-data ownership, and it can still be a pain, like when I download a plugin say from hosted to local using filezilla, have to get into the shell and do a sudo to change the ownership etc..
    Previously I installed themes and plugins, and updates, images and media. ALL owned by my Linux user account. World readership was all apache needed.

    Suggest that you use the “net” tab (or equivalent) on your browser inspector to see which resources it is stalling on. Very likely they will be things that have something wrong with their net address or path etc.

    In the step where you said you replaced the domain name with the IP address, did you do a straight database text replace ? Or did you use a plugin such as “Better search replace” that adjusts serialised data ?

    I have had similar problems with commercial themes which dropped out of their author’s catalogue, hence even repurchasing the theme was not an option. I have not seen this as such a problem with free themes for some reason. Overall I feel this discourages me from using commercial themes.

    On one occasion a site went weird because a WordPress update changed the javascript version, previously innocent errors now mucked up the accessibility, I had to revert to the older WordPress version and block auto updates. I then fixed the js errors.

    Another variation of this problem I have had is when the minimum PHP version changed, had to debug and update some code of obsolete plugins and theme files.

    What I do @jgstroup, is to configure my localhost webserver to use the “VirtualHost” method, then with the “hosts” file direct my domain name to localhost, by commenting the lines in the hosts file on or off I can rapidly switch between web hosted and localhost servers if required.

    I usually go to the trouble of making the database name and database user the same as will work in my hosting, thus even the wp-config.php file migrates unchanged.
    With the exception of SSL and services such as SMTP for sending email, my websites barely know that they have been moved between localhost and hosted.
    I have never bothered with SMTP on localhost, I just leave that till it is hosted.
    I have gone to the trouble of self signing an SSL certificate and configuring the security exception in he browsers.

    In fact, much of the WordPress documentation and tutorials use the example of using “localhost” in lieu of a domain name. It seems to me that this is a Red Herring and a disservice to new WordPress users.

    I totally agree.

    Links to useful documents include:
    https://en.wikipedia.org/wiki/Hosts_(file)
    http://httpd.apache.org/docs/current/vhosts/
    http://httpd.apache.org/docs/current/vhosts/name-based.html

    • This reply was modified 6 years, 3 months ago by RossMitchell.
    • This reply was modified 6 years, 3 months ago by RossMitchell.

    Bottom line is that there MUST be a difference, certainly the apache server can tell the difference.
    What about directory and file owners and permissions ?
    Thanks for posting the .htaccess file, see the line:
    “RewriteCond %{REQUEST_FILENAME} !-f”
    It translate as “if the file exists, then do not rewrite”, this test is failing !
    Have you done any SSL configuration ?
    What is in the apache “sites-enabled” configuration files ?

    A site I created was hacked much like yours, odd .php files etc.
    – I got the creation dates+times of the rogue files and directories.
    – I went to the access logs and looked at what has happening at these times, I also have a journal file of user logins, this let me put together the full story.

    The bottom line was that an administrator account was hacked using a user + password scanner.
    The hackers uploaded their own plugin, the plugin was highly obscured using lots of base64 and rot13 functions, what it did was an “eval” on whatever [POST] parameters passed to their plugin loaded file. Since POST data is not logged I have no clue what they did. Of course I could see which files they were accessing.
    I disabled the hacked admin user login, renamed their plugin directory, took the website offline by renaming the website root directory.
    Rebuilt the website, scanned the database for weird stuff and reloaded it.
    Months later I still get hundreds of login attempts a day that trip lockouts.

    May I summarize what we know about your configuration using what you have told us, and point you at what you need to do next.
    1) Your apache server is installed and able to display the base HTML file “It works”
    2) You have not tested that PHP is configured or working.
    3) You have not tested that the database is configured and working.
    4) You need to configure apache to map a network name to the website root directory. I would suggest that you use the “VirtualHost” scheme.
    You may end up using settings like these in your “sites-enabled” files:

    <Directory /home/ross/web>
     Options Indexes FollowSymLinks
     AllowOverride All
     Require all granted
    </Directory>
    <VirtualHost *:80>
    DocumentRoot /home/ross/web/project
    ServerName domainName.com
    ServerAlias www.domainName.com
    </VirtualHost>
    

    5) Test your work on pt 4 by loading the WordPress supplied file
    http://domainName.com/readme.html
    6) NOW you can run the WordPress install script
    http://domainName.com/wp-admin/install.php this will most likely clear pts 2 and 3 above, otherwise you will have to fix the issues by searching and asking on other forums since these are not WordPress issues.
    7) Do even more configuring if you want to use SSL (https)

    I am sure you will learn a lot.

    • This reply was modified 6 years, 3 months ago by RossMitchell.
    • This reply was modified 6 years, 3 months ago by RossMitchell.

    Firstly you need to tag a thread with “modlook” to get the type of attention you ask form
    Secondly, as I understand the rules, that you do not like a post may not be a good enough reason to have it deleted.

    The SPF all looks ok.
    Of course there can be many reasons an email client tags a message as spam, SPF is just one of them. Other reasons include the content of the email, the words and phrases used.
    Are you sure that the email is being put into the spam folder because of SPF ?

    Yes it is. This makes sense when you are developing or otherwise working on your website personally. It makes little sense if you are hosting the website for the world to view.

    I would suggest that you download and install one of the many bundled configurations of Apache+PHP+mySQL, such as LAMP, MAMP, WAMP or AMPPS
    Then use the “VirtualHost” method to work under your domain name rather than some variation of “localhost”.

    From:
    https://support.gfi.com/hc/en-us/articles/360013000093-How-to-check-and-read-a-Sender-Policy-Framework-record-for-a-domain

    Using it on your domain looks reasonable.
    How well does it work when you send an email ?

    Is that the one we have to update in SPF record.?

    YES. Add this IP address to your spf record.
    The spf record must list ALL the IPs or names of servers which you authorize to send your email, do not remove entries from the list unless you know that you are never using that server.

Viewing 15 replies - 241 through 255 (of 3,259 total)