tullphd

I will usually create a “Test Page” to test my widget code. After I perfect the widget in the “test page” then I place the code in a TEXT widget box item and place it in the right position under appearance/widgets/ >>>>.

just remember to keep the test page in draft mode after the test is completed so that it isn’t active on the site.
when testing you can switch from visual to text and utilize the WP tools in the kitchen sink for images, ect to make great widgets.
Unless your a master code writer that can just create code that works perfectly on the fly.

inspecting element:
<img src=”https://www.endopals.com/blog/wp-content/uploads/2014/05/cropped-embrace-you-1700px1.jpg&#8221; class=”img-responsive” alt=””>

you don’t have align center in the code!

what is the URL?

clear your cash in your browser and see if that clears the browser.

what is the URL?

just put the [slider code] in the php header code area where you want it.

Play with the padding to get your text to wrap better.

change <img class=”alignleft to:

<img class=”alignnone size-medium wp-image-372″ src=”https://keepitrealrn.com/krrn/wp-content/uploads/2014/05/IMG_0323-300×195.jpg&#8221; alt=”IMG_0323″ width=”300″ height=”195″>
_____________________________________________________________________
I would also change the name of the file for better SEO, and then also change the ALT tag to something meaningful, such as [Captain at the helm of KeepitRealRN ]

with an <alt Tag> of “IMG_0323” it doesn’t help your SEO at all, Naming pictures, and alt tags is important in making the site work for you. I realize that perhaps just giving them some #(???001,002,003) is easy but wrong, for effective site SEO rankings.

Additionally:
https://snapknot.com
This site is not a responsive web design, It works on a monitor in a full browser window, but if you scale the window it DOES NOT scale content, to other media, iphone, tablet, landscape or portrait viewing.

As you will see in one of my sites : https://tinasluxurioussheets.com/
which was built on AVADA 3.4.3

just load the page and shrink your browser window down small like an iphone, or tablet view.

You can make a better site than the one that you are trying to duplicate with some study and research in WordPress.

The site you are referencing IS NOT A WORDPRESS CMS site:
Based on my limited evaluation- sorry,

So there is not any theme that created this.

if you try – https://snapknot.com/wp/wp-login.php
or: – https://snapknot.com/wp-admin
it pushes a 404 error (Unless I’m mistaken this should load a login page. This site does not retrieve the php login.)

I also searched the source code and usually under the title </>
you would see a <style> …… </style> something like the following:

<title>Tina's Luxurious Sheets | Sleep on a cloud tonight</title>
<style type=”text/css”>Avada_3.4.3{color:green;}</style>

Where the theme:( AVADA 3.4.3 ) designates the theme and version.

Your referenced site I couldn’t find :theme code:
<title>
Wedding Photography | Wedding Photographer Directory
</title>

but, you can design around the theme of your choice and utilize the following plugins to handle your sign-ups requests.

— signups,
— people creating profiles, upload work,
— set the charging fees but also for me to charge them monthly subscription fees etc.

you will need: (plugins!!!!)
1. woocommerce, (ecommerce) FREE
2. woocommerce subscriptions, i think $199.00 (— set the charging fees and charge them monthly subscription fees etc.)

Many other Additional plugins of course can deliver appearance and functions.

For additional info just contact the webmaster at the site and see what they are willing to share with you.

There is NOT just a magic button to make the site as you would wish.

What theme are you using?

What you are looking for is a “Sticky Header”, at least this is one way to accomplish what you are wanting.

See this site: worldhenge.com (under construction) …
There is a main header that is fixed at the top of the page, and when the scrolling page extends farther down a “Sticky Header ” appears which has the logo and main menu for navigation (Variably Transparent above content).

This is a theme feature of “AVADA” one of the best themes in the world.

Other than an out of the box feature as mentioned, Coding this would be required. Or search for “Sticky Header” plugin:

look for Sticky Header by ThematoSoup, [https://thematosoup.com/] others will also be choices in wordpress search.

conflicting plugin issue: I deactivated>> Nav Menu Roles, and menu loader work perfectly,

Also this plugin was responsible for not being able to remove widgets (tried to move widgets to deactivated state) that I was having trouble with yesterday, Huh

Nav Menu Roles
Hide custom menu items based on user roles

Version 1.4.1 | By Kathy Darling | Visit plugin site

Just ftp your server, delete the folders which have all the wordpress stuff in it:
wp-admin
wp-content
wp-includes

Then re install WordPress.

then start over

withing the folders you could eliminate individual folders as well to delete plugins, images, but to wipe it out and start over just delete the above listed folders and all of the folders content

tried validating the code: errors
Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Warning Unable to Determine Parse Mode!

The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:

in Direct Input mode, no MIME Media Type is served to the validator
No known Document Type could be detected
No XML declaration (e.g <?xml version=”1.0″?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns=”https://www.w3.org/1999/xhtml&#8221; xml:lang=”en”>) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.

Info No Character encoding declared at document level

No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.

See this tutorial on character encoding for techniques and explanations.

Info Using Direct Input mode: UTF-8 character encoding assumed

Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator’s form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.

If you notice a discrepancy in detected character encoding between the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document.

↑ TOP

Validation Output: 2 Errors

Error Line 1, Column 1: character “{” not allowed in prolog
{\rtf1\ansi\ansicpg1252 {\fonttbl\f0\fnil\fcharset0 CourierNewPSMT;} {\colortbl…
?
Error Line 1, Column 688: end of document in prolog
…w0\kerning0 \outl0\strokewidth0 \strokec2 \uc0\u8234 \uc0\u8236 \ \uc0\u8236 \
?
This error may appear when the validator receives an empty document. Please make sure that the document you are uploading is not empty, and report any discrepancy.

tried validating the code: errors
Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Warning Unable to Determine Parse Mode!

The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:

in Direct Input mode, no MIME Media Type is served to the validator
No known Document Type could be detected
No XML declaration (e.g <?xml version=”1.0″?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns=”https://www.w3.org/1999/xhtml&#8221; xml:lang=”en”>) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.

Info No Character encoding declared at document level

No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.

See this tutorial on character encoding for techniques and explanations.

Info Using Direct Input mode: UTF-8 character encoding assumed

Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator’s form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.

If you notice a discrepancy in detected character encoding between the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document.

↑ TOP

Validation Output: 2 Errors

Error Line 1, Column 1: character “{” not allowed in prolog
{\rtf1\ansi\ansicpg1252 {\fonttbl\f0\fnil\fcharset0 CourierNewPSMT;} {\colortbl…
?
Error Line 1, Column 688: end of document in prolog
…w0\kerning0 \outl0\strokewidth0 \strokec2 \uc0\u8234 \uc0\u8236 \ \uc0\u8236 \
?
This error may appear when the validator receives an empty document. Please make sure that the document you are uploading is not empty, and report any discrepancy.