Joseph W

Hi Jason!

The background image and text scaling for that section on your Home page can be adjusted by editing the page content.

Once you have the editor for your Home page opened, locate the Device Views icons and click the one that looks like a phone to switch to the mobile display mode. You can adjust the widths of the columns for the mobile display by clicking and dragging the edges of one to make them larger and allow your text to span the entire width of the section, which should help prevent it from getting bunched up like you are seeing now.

Adjusting the position of the background image will be a little trickier, but hopefully it won’t prove to be too difficult! Use the tabs located in the top right of the content area of your page and switch from Visual to Text mode, this should show the raw HTML of your page content. Look for the inline rule background-position: 50% 50%; on that first section and change the first 50% (the horizontal position) in that rule to 80%, it looks like that setting should align your background as desired.

Please let us know if you have any questions about making these changes and we will do everything we can to help!

Hi Mike!

I can’t say for certain, but it is possible that the vanishing cron events might also be related to GoDaddy’s Managed WordPress platform. I found some threads in their support forums with conflicting information and you should probably reach out to them for clarification on this matter.

One topic suggests that WP-Cron should be allowed even though the the system level Cron is disabled. However, I found two other threads stating that WP-Cron events were not working as expected for those users.

Hopefully GoDaddy can help you figure out why WP-Cron isn’t working and please let us know if you have any other questions for us!

Hi littlepellizza,

I am happy to hear that you were able to find the source of the conflict!

I did some additional testing and it looks like the conflict with Advanced Editor Tools only occurs in the latest version of the Post and Page Builder, everything seems to work as expected when using the previous stable version 1.20.2.

If you only need the Tables feature from Advanced Editor Tools then you might want to try using the Tables option that was added to the latest Post and Page Builder version to see if that helps you work with your website content.

Alternatively, if you prefer using the Tables from Advanced Editor Tools, then you can install WP Rollback on your website and change the Post and Page Builder back to version 1.20.2.

I created a bug report with our development team to see if we can address this particular conflict in a future release, but I cannot provide any kind of estimate on when we will actually be able to fix the conflict.

Hopefully one of those solutions allows you to work with your tables again and please let us know if there is anything else that we can do to help!

Hi littlepellizza,

Our developers found an issue with the version of the Post and Page Builder that was being distributed by the WordPress SVN, there was a JavaScript file missing from that distribution. Fortunately they were able to get the error corrected and all of the correct files should be going out now.

One way to ensure that you have the distribution with all of the files in place is delete the Post and Page Builder from your website completely. Then, instead of reinstalling the plugin through your WordPress admin, download the plugin Zip from the plugin page on www.remarpro.com using the Download button there. Once you’ve downloaded that Zip file you can then manually Upload it to your website under Plugins > Add New.

The previous distribution was missing the tinymce_tables.min.js file in the assets folder, and I just confirmed that the Zip downloaded from the www.remarpro.com page has that file in it.

After the correct plugin distribution is installed I would then make sure that your Pages and Posts are configured to load the Post and Page Builder tools by default. You can set the default editor type by navigating to Post and Page Builder > Settings in your WordPress admin where you will see a series of dropdown menus that you can use to set the defaults.

I hope that helps you get things working as expected and please let us know if there is anything else that we can do to assist you!

Hi littlepellizza, sorry to hear about the problems with the recent update.

I just tested out the latest Post and Page Builder version in one of my environments and so far I have not been able to replicate the problem shown in your screenshot.

My first suspicion is that this error is being created by some kind of plugin conflict with the recent update. You can test for a plugin conflict by temporarily deactivating all non-BoldGrid plugins and then loading the editor. If the controls start working as expected then one of those other plugins is most likely the source of the conflict.

If the controls start working after the deactivations then you can start reactivating your other plugins one by one to find out which one is causing the conflict. Assuming that this is a plugin conflict, could you let us know which plugin is incompatible with the latest Post and Page Builder version?

The problem could also be related to a bad update, deleting the Post and Page Builder and then reinstalling should help ensure that you have the correct plugin files in place.

Hopefully we will be able to help you get this sorted out soon!

Hi zenbob1,

I did some additional testing and I see exactly what you mean.

The Add Media button is a core WordPress feature and is not provided by the Post and Page Builder, which likely explains why it works when editing an FAQ.

In my testing the Add Block button was shown on the page but clicking it did not open the block interface as expected. Do you see the same behavior on your website?

I created a bug report with our development team to investigate this problem further, but I am uncertain if or when we will be able to make any changes on our end to address the incompatibility.

Thank you for reporting this problem to us and please let us know if you have any other questions!

Thank you for reporting this to us siprof!

Out of curiosity, where does WordOps put wp-config.php if it is not in the web root directory? Is there some kind of special subdirectory that they use for all WordPress core files or is wp-config.php the only in a different location?

It sounds like we might need to make some changes to account for additional non-standard configurations and we appreciate any information you can send us!

I am happy to hear that worked for you!

It looks like the editor selection dropdown will only display on Campaigns when either the Classic editor or Post and Page Builder is selected in the Preferred Editor settings. Setting that option to Default seems to load a version of the Classic editor designed by Charitable to work with their Campaign items.

Please let us know if you ever have any other questions for us!

Hi ashewebmaster, sorry to hear about the issue with the editor for that particular Charitable Campaign item.

I did some testing and it looks like the problem is that Charitable Campaigns are not compatible with the WordPress editor and requires the Classic editor’s backend to function properly.

Changing the editor type with the dropdown provided by the Post and Page Builder saves that editor selection in your website’s postmeta table so that same editor is loaded whenever that post is edited in the future. This is clearly a problem in this instance since your post is attempting to load using an incompatible editor type.

The first thing that you will need to do to get the editor loading for that Campaign is to find the ID number associated with it. Fortunately Charitable makes this easy and you should see the ID number displayed next to the Campaign’s title in the Campaigns list.

The next step is to open up the postmeta table for your website using your database management tool. Look for a row in that table that has that post_id along with _bgppb_default_editor in the associated meta_key field. You should also see that the meta_value for that entry is modern. Delete that row to remove the saved editor selection recorded by the Post and Page Builder. Once that is finished your Campaign should revert back to whichever editor is selected for Campaigns in the Post and Page Builder settings.

Hopefully that fixes the error you are seeing and lets you work with that Campaign again!

Hi silvergs-

It’s been a while since we heard back from you on this issue, so I’m marking the topic as “Resolved.” Please feel free to reply or create a new topic if you have any more questions!

Hi ashewebmaster,

I was able to replicate the problem you described and right now it seems like there is a bug with the Preferred Editor selection tools in the Post and Page Builder.

We now have a ticket in with our development team to investigate the issue and hopefully we will be able to get a fix released in the next update.

Thank you for reporting this to us and please let us know if there is anything else that we can do to help!

Hi 2albion,

The translucent shape that shows up on your home page is added by one of the Inspirations starter content sets and the easiest way to remove those styles is to use some Custom CSS. The following snippet should remove those designs from your website as expected.

body.home.inspirations-theme-73:before, body.home.inspirations-theme-73:after { border: none !important; }

Please let us know if there is anything else that we can do to help!

Hi RitoRawling,

It’s been a while since we heard back from you on this issue, so I’m marking the topic as “Resolved.” Please feel free to reply or create a new topic if you have any more questions!

Hi washingtonhdmf,

It’s been a while since we heard back from you on this issue, so I’m marking the topic as “Resolved.” Please feel free to reply or create a new topic if you have any more questions!

Hi @silvergs,

I saw that our support team responded to your ticket on our website with the fix for this problem and I wanted to post the solution here just in case any other users run into a similar issue.

It looks like the caching plugin installed on your website was preventing the correct styles from rendering properly and once that plugin was deactivated the website started displaying as expected.

Hopefully things are working for you now and please let us know if you ever have any other questions for us!