katdidit

I think that you might want to open a ticket with Avada, in the meantime you might try disabling plugins one at a time and rule out a conflict. The only error it seems to be generating is a “WebSocket Error: Network Error 12030” related to visual composer and might have something to do with memory, but because the shop and other pages work fine and it is only loading your scripts up to your google tool tips and stops before it loads the rev slider on the blog post so that would be the first plugin I’d disable.

Good luck with it.

Have you set the product created as virtual/download? I believe that skips the shipping but still will collect the customer name etc information which is then passed to paypal along with the pricing.

Just curious, how did you fix the problem?

You are missing the meta tags for rich snippets on your page. For an explanation see this: https://moz.com/blog/meta-data-templates-123. There are many plugins (sharing and SEO) that will do this for you. Possibly the best is by Crunchify, because theres not a lot of overhead. They also have a DIY tutorial here: https://crunchify.com/how-to-create-social-sharing-button-without-any-plugin-and-script-loading-wordpress-speed-optimization-goal/

Hope this helps you.

• This reply was modified 7 years, 8 months ago by katdidit.

Oh dear.
If you right click on the form and choose inspect element most browsers will pop up an applet window that tells you the html structure and css rules that are affecting the forms and phone number, and what line of the stylesheet they are on. You can also play with/edit the rules to see how it will look. Hopefully you are using a childtheme, then open up your bulksealer stylesheet and a) for the Contact 7 form, copy/note the classes for the form usually starting with I think its’ “wpfc7” either and add your new rules to widen the width, adjust the padding and otherwise adjust the form. Same goes for the header phone number. For instance right now your phone number has the rules

.header-top .container .call-us {
float: right;
height: 44px;
line-height: 44px;
font-size: 15px;
text-align: left;
color: #333;
padding-left: 27px;
padding-right: 48px;
}
in your main.css file on line 267 – to make the font bigger edit the font-size rule to the size that looked good to you in your inspector panel

For the form order on the page it looks like the shortcode is in a widget or separate page frame, you need to put the shortcode into the main page where you want to place it.

Hi Debbie – Go into your CPanel file manager, or use FTP and change the name of the nexgengallery folder located in wp-content/plugins folder and you should be able to access your site again.

Do you have a backup you can look at? Just curious what plugin are you using? You might also want to look at your “from” emails in your settings, for most setups it should be an email from your domain (it doesn’t matter if its real in most cases) otherwise you end up with dkim errors.

Actually he is doing you a favor by not using the install from the webhosting company. The way to make sure that he does not control you server and domain is to grant him a separate user access that is not connected to the billing and main user sign on, but some web hosts do not offer this feature tho cpanel has made some strides in this area. If they offer this and how to use it, is what to ask of both your domain and hosting providers.

The other thing to ask is if you do not trust him, why did you hire him?

You would not necessarily receive emails directly from the new users, only from the wordpress/woo systems – It sounds like what you are receiving are the notification emails to let you know that they have registered. Part of that registration is that an email is required, which is what the emails are referring to the generating the username.

If you are concerned that the new registrations are not legit, you can review the users for that, and then try an anti-spam measure like google recaptcha, which is a fairly simple plugin and woo friendly. You will have to register with google developer api to get your keys, but that also is fairly simple and the plugin (I believe) has some instructions and a link on how to do that.

Update 1.9.1 solved this. Thanks.

If you deactivate the theme for a wordpress stock theme (temporarily) and the comments work then you will have it narrowed down to the theme and then maybe you can ask the theme author to fix/update it.

This is a jetpack error. I think maybe starting a thread with them might be more helpful for you. The only advice I can think of is the standards to make sure you have comments enabled in the admin settings, try deactivating your plugins, one at a time and then the theme (switch to wordpress stock theme Twentyseventeen) and trying to post a comment after each change, to see if there is a conflict. You might also try deactivating the jetpack plugin and reactivating it to see if that helps.

You need to add the pseudo code :hover as well as the regular selectors. .noshadow,.noshadow:hover {box-shadow:none} –

also if you use both classes in one selector ie “[class*=”wp-image”].noshadow”, “[class*=”wp-image”].noshadow:hover” you can lose the !important on the border and background rules since the [class*=”wp-image”] is adding the box-shadow and the border to all images. By using both selectors in one you are making sure that the [class*=”wp-image”] isn’t overriding it in other style sheets (responsive or bootstrap) as well.

Try using “none” rather than transparent and border: 0 if that still isn’t giving you what you want.

Was able to solve this by adding ob_clean(); right before the mdpdf output in the plugin function file.

Add a second class to the images that you don’t want to have a shadow
[class*=”wp-image”] .noshadow {box-shadow: none;
}