doubledworks

Ok thanks for that Tom

That could work in some instances though it can also potentially change the layout depending on the screen size if the paragraphs fall in an order which changes the context.

I may have to look at another way to do this.

Can you briefly explain what equal_heights=”false” is used for/applied too ?

Hi Tom

Here’s a screenshot

I want to move paragraph 3 up further under paragraph 1.

I could have sworn i did this at one point using equal_heights=”false”

Cheers

@mb4886

I just noticed “equal heights” functions a little like “last=”true” depending on whether “equal heights” is set to true or false.

Make sure you’re using last=”true” within the shortcode of the last paragraph something like this.

[lgc_column grid="100" tablet_grid="100" mobile_grid="100" last="true" style="padding-left:10px;"][contact-form-7 id="9" title="Contact Form"][/lgc_column]

Yeah.

It’s just laid out a bit differently but it’s still much the same.

Other than the plugin you’re using now and the CRM plugin the other four are almist identical with slight variations focusing on one of the four main modules.

Payment / invoicing
Contact form
Scheduling / events
Livesite widget

So theoretically you can actually use any of those four plugins but the booking events plugin is the most specific for events scheduling out of the box.

If you dont use scheduling but you use say contact form then you can install the contact form plugin if you like, and so on.

Check them out

There’s still no suggestion when or if this issue will be resolved however you can use this plugin instead which uses the new code base.

Apparently you wont loose any previous emails and contact history etc.

This error has been an issue for at least 10 months. I have just asked premium support to fix it again. It was suppose to be fixed in the new plugin which was released approx 2 months ago. Clearly that didn’t happen for one reason or another.

The error doesn’t appear to make a difference to how the plugin works though and if you add the following line to your wp-config.php the error will no longer be visible on your site.

define(‘WP_DEBUG’, false);

With a bit of luck it will be fixed for the next release.

I see those lines in my .htaccess file.

My plugin is set to block on both XML-RPC features so why would Jetpack remain connected when it relies on XML-RPC?

When i used ithemes security some months back and prior to the latest XML-RPC blocking feature, it blocked Jetpack.

Has something else changed?

Is the description stating it blocks Jetpack outdated and need updating?

Surely Jetpack should completely stop working when XML-PRC features are set to block?

I wouldn’t but you probably could. Many of the features are the same so there’s not much point. iThemes Security actually uses Sucuri to scan for malware too though not to the same degree. Using more than one of these plugins could get rather resource hungry as well.

I assume this attack is due to the latest xml-rpc vulnerability which iThemes suggested was brought to their attention via Sucuri. Since then an additional feature was added below the original xml-rpc feature to provide a second layer of protection and appears to be okay to set to block when using Jetpack and the like.

Having said that I found this post while searching though the forum as it appears Jetpack will work even when both xml-rpc settings are set to blocked. This is as most will be aware contrary to what this plugin suggest should happen.

I assume this is a bug following the addition of the recent xml-rpc feature.

If anyone knows what’s causing this it would be much appreciated.

I know what you’re saying. I realize the files are or at least can be a separate issue. I completely get that there is an ID issue with merging. What about with this sync example though?

I am likely missing some aspects required here because I don’t write software and this is a very simple explanation of what would be required in reality however what I was thinking is firstly that, if the site pulling and pushing data was known to the software / plugin via a setting as the DEV and or production site and providing content is only pulled from the production site to the DEV site and then inserted deleted etc to the production site, it may help.

So first off you would pull the production site to the DEV in its entirety. (WP Migrate DB pro or duplicator etc can do this job well already.)

Then if there was a date range setting (IE from what ever day the data was pulled down (until the data insert, delete etc date) in the plugin / software allowing the complete exclusion of data outside of the set date range, while data inside the range is compared by date, ID and GUID, content, revision, etc and based on where it exists at the time. IE DEV or production.

Whether the content differs by ID/GUID and or content and providing its the latest revision only, that data could perhaps be stored to a file that you can later run to insert the new data which is not currently in the production site. So you would also exclude new data already in the production site from being inserted as its not required because it already exist.

At this point like any data inserted into the database, it could generate a new ID/GUID and maybe even time and date stamp.

This way if another entry has been added to the production site using the same ID or GUID as the entry coming from the DEV site it could be altered by ID etc to work in with the production site, as these entries haven’t been accessed/used by RSS etc yet as they are coming from DEV so it doesn’t matter if the ID changes. Well not to my knowledge anyway.

So in other words, you cant duplicate and confuse entries by ID because the database would just create the next sequential ID number upon each row being inserted.

Therefore deleted posts on the DEV site could also be deleted on the production site because the data and IDs no longer exists on the DEV site and as it compares all data between the date range and its only designed to push from DEV up (not push from Production down) so it could safely assume it was removed and introduce a delete string to remove it from the production site.

Of course the production site would potentially need to be in maintenance/unavailable for a short period when you do this so no new data is entered during the process but it wouldn’t need to be offline while building and testing the DEV site, just while doing the final insert etc and test to make sure it all works. So maybe an hour or something as oppose to days or more.

Just a thought. I have no doubt it would requires some magical coding but I would like to think someone could make this concept work or something like it, if it isn’t already out there somewhere.

———

So how is one suppose to get updates from a DEV site into the production site without overwriting the changes made to the production site, while building and testing the DEV site. Do you have to manually finding and re-enter each new row? Surely there is some easy way of doing this if it isn’t such a big deal?

Please explain how its not a big deal. I’m very keen to know how to do this and where to look to understand how its done without breaking stuff.

I still believe there has to be some sort of solution for this. Surely it would be impossible to manage a big site without some sort of solution?

Yes from what I can see the database is the main issue.

It seems crazy if there is no solution. Surely this has to be one to manage any live site if you test build on a dev/staging site.

Is this specifically a wordpress issue or are other cms sites like drupal, jamola and the like in the same boat?

I cant see how sites like wordpress.com and www.ads-software.com could possibly survive without some sort of solution.

I cant get my head around there being no solution. Surely there has to be something?

Anyone have a solution? Anyone working on a solution?

Here is one of my current test sites.

https://doublednetworks.co.nz

Click any link and the page will completely reload.

Just so you are aware, the vcita active engage feature turns on the contact link in the bottom right corner of each page.

Whoops, i see i misspelt it. Vcita, not Victa

https://www.ads-software.com/plugins/meeting-scheduler-by-vcita/ is the plugin.

I have sent them the exact same query. I don’t get a problem until I update the AIOSEO plugin with the active engage enable on Vcita. I can update all other plugins without problems including Vcita.

It has to be one of these two plugins causing my pages to completely reload. By that I mean it loads like an HTML site whereas database sites should just pull in the new info and the other info should remain static to the eye.

The issue may have in fact occurred in a previous update. One prior to the last as i haven’t been able to update my site for a few weeks due to a separate unrelated issue.

It looks like the new updates cancelled out the old stale entries. Nice.

After waiting approx 24 hours and testing the installation twice, it now appears to work fine. Given the problem appears to be resolved and I created this support thread I am marking this issue as resolved.