Happy Coder

Thank you.

Will V2 still use jQuery?

As it stands V1 is quite solid except using jQuery, whereas the issues for V2 are quite numerous looking at the repo.

Do you think or are of the impression that V2 is so much better than V1?

Thank you.

Checked the repo and could not find jQuery except in these two files

https://github.com/thriveweb/photoswipe-masonry-v2/blob/master/frontend/js/photoswipe-masonry.js

https://github.com/thriveweb/photoswipe-masonry-v2/blob/master/frontend/js/photoswipe-lazyload.js

Proposal, what would it cost to have your guys write that in vanilla JS?

Happy to pay for a vanilla JS version of this plugin. Photoswipe itself is vanilla JS, that being one of the reasons what makes it so fast.

Would get cracking at it myself however still learning. Seeing that the old version uses jQuery in \wp-content\plugins\photoswipe-masonry\photoswipe-masonry.js made me sad as this is a HUGE payload for the site. Generally I am trying to keep away from an plugins that use jQuery. Writing it all in vanilla JS could speed this thing up plenty fold.

Managed to get 100% on the GPSI (Google PageSpeed Insights) score though by inlining the jQuery load and moving registered and enqueued stylesheets and script to footer and partly loading them async. However all this can be avoided with some vanilla JS.

What do you think?
Also is the repo you linked under active development?
There are lots of issues/improvements happening, be sure I am watching this very closely. Thank you heaps for your effort. Let me know if I can be of any help, thank you. Perhaps you could get donations going to support your dev time? I am sure if a couple of people support your work hours this could be done in no time.

• This reply was modified 7 years, 2 months ago by Happy Coder. Reason: added more text

Due to help from @schlessera and @danielhuesken on the #cli WordPress Slack channel I found out what I had to do.

Instead of setting a PATH value in the Windows environment variables I had to make a **new** variable called WP_CLI_PACKAGES_DIR and set the value of that variable to C:\Users\YOUR_WINDOWS_YOURSERNAME_HERE\.wp-cli\packages.

I also had to create the folder packages under C:\Users\YOUR_WINDOWS_YOURSERNAME_HERE\.wp-cli\. The folder was not created automatically.

After that though Composer was complaining that PHP does not have enough memory and so I permanently increased the memory from 128M to 512M in the php.ini file.

Now I could install the wp-cli package just fine, ran it and it also worked perfectly.

Reference links:
https://superuser.com/questions/949560/how-do-i-set-system-environment-variables-in-windows-10

https://make.www.ads-software.com/cli/handbook/common-issues/#php-fatal-error-allowed-memory-size-of-999999-bytes-exhausted-tried-to-allocate-99-bytes

Yes would be great to inform users about the upper- and lowercase differences on Windows and Mac systems regardless of the plugin’s capabilities.

Basically stick to lowercase table names.

Thank you Cory.

Hope this did the trick for theokoopman as well.

@theokoopman Would be interested to hear from you if this solved the issue for you.

Given this post by plugin author I am resolving this issue.

Yes would be great to inform users about the upper- and lowercase differences on Windows and Mac systems regardless of the plugin’s capabilities.

Thank you Cory

To avoid problems caused by such differences, it is best to adopt a consistent convention, such as always creating and referring to databases and tables using lowercase names. This convention is recommended for maximum portability and ease of use.

https://dev.mysql.com/doc/refman/5.7/en/identifier-case-sensitivity.html

Quite simple. User lowercase for your WP table prefix in wp-config.php and you are fine on any host and with Duplicator.

Happy to post the fix.

https://www.ads-software.com/support/topic/duplicator-creates-a-new-install-not-a-duplicate?replies=38#post-7752708

and

https://stackoverflow.com/questions/5659835/xampp-and-mysql-all-colimns-in-table-are-lower-case-in-php,

particularly, this answer

https://stackoverflow.com/a/8587744

was the solution for me.

If you are on Windows or Mac using XAMPP, WAMP, etc. and you want to use case senSiTiVe characters for your table names, so to speak, if you set a case sensitive table prefix in your wp-config.php like so

$table_prefix = 'hfjRhjgvnjmDzgnme_';

then you must set

lower_case_table_names = 0 in your my.ini file

in the [mysqld] section of that file.
Find the my.ini file in the \mysql\bin\ folder of your XAMPP or WAMP installation.

And then you must deal with the warning that Duplicator correctly throws you during scanning.

Though your MySQL databse will be restored correctly with case senSiTiVe characters as table prefix to the host/server!

Duplicator works regardless of this MySQL configuration! Attention there Windows and Mac users!

Depending on where you restore the archive to the MySQL configuration might be different, it can happen that WP does not recognize the WP install because the table prefix is all lowercase and because of that WP throws the install screen as it wants to create a new set of a database.

3. For table name case sensitivity issues either rename the table with lower case characters or be pre-paired to work with the lower_case_table_names system variable setting.

[would be good to change per-paired to prepared]

So do we have to use lowercase table prefixes on Windows and Mac machines if we want to work with various hosts?

Are lowercase table names the (preferred) standard?

I assume so since many hosting companies are based on Linux systems, no?

Duplicator does the job right, though the table names are borked if you are on Windows or Mac and use UPPERCASE characters in your table prefix.

So basically the chances are quite high of someone running into this error. Attention there users, this is not really Duplicator related.

How could Duplicator though kind of warn users on Windows or Mac systems about the use of UPPERCASE characters as table prefix?

Might have a fix for you.

Can you just quickly confirm, you are on Windows machine obviously (WAMP), and I guess you have CAPITAL letters in your wp-config.php file as $table_prefix values, right?

Something like: $table_prefix = 'CapitaAl_';

If you do, try using only lowercase characters as $table_prefix values and see if that works. Curious to see if that helped you.

Kind Regards

Jan, following forum etiquette since day one but thank you for letting me know.

More important, this situation is different because of these key points.

1.
The other person that has this issue and keeps having this issue has marked the thread as resolved but the solution is not given.

2.
The other point, that server versions differing might be the issue is also ruled out and confirmed in that other person’s thread.

3.
The other person’s issue is exactly the same issue I am having, so not distracting from other people’s problems but rather letting the devs know that there are multiple people suffering from the same issue possibly directing more interest for this issue.

4.
When I come to the support forum to check for people with similar issues I was at first happy to see a resolved thread with the issue I am having. Quickly did I have to see that in fact this is not resolved, neither for the other person or for myself.

These are the points that led me to posting that I am having this issue too.

I am now going to post a last time in that other person’s thread, simply stating that I am also having exactly the same issue. Please do not delete this post because of the above mentioned points.

Thank you for your understanding and help.

Also see here, server versions are the same.
https://lh3.googleusercontent.com/-XrufIXDPbYE/V3-SW7zVcwI/AAAAAAAACNs/YJHd9V2cd14kvXL3cNotLYLakL8T00T7QCCo/s0/Duplicator%2B003.png. This is already installer.php running on the host with db setup freshly and ready to deploy.

Did check out this thread https://www.ads-software.com/support/topic/site-not-online-just-a-blank-wp-install?replies=4 but the error cannot be due to server versions differing.

If you like I can set up a subdomain with user and pass and give you access to run the restore yourself. It is a basic approx. 8MB file to restore the default WP 4.5.3.

Whatever I do I get the WP fresh install screen showing up.

Thank you for your reply.

You mean in Archive – Files – IF Enable File Filters IS TICKED only then the Directories and File Extensions that are given WILL be skipped, BUT if they are not selected as per default setting then all directories and files will be backed up. Do I understand this correctly?

Regards

SOLUTION

WordPress Importer Redux

https://github.com/humanmade/WordPress-Importer

SOLUTION

SOLUTION

WordPress Importer Redux

https://github.com/humanmade/WordPress-Importer

SOLUTION

Have 2 hosting plans, a fast local one (meaning from a local business that is rated #1 in the country I am in) with 35GB space, unlimited domains, traffic and mysql dbs. Fast support, nice people, good setup, SFTP, etc. all works.

The other one is “Happy Hosting” from DreamHost and I can only really recommend DreamHost. Never had a single hiccup with them so far. Just starting out but already 50% of the cost of these two plans is being paid by clients that host their websites I developed with the plans. With a few more clients the hosting will pay for itself, then I might upgrade the plans and pass on the benefits to my clients without charging them extra.

I thought the warning means that files over 3MB won’t be backed up.

Your last reply did make this crystal clear now. No use in changing the setting in that case, thought by changing the setting I can tell it to also backup files over 3MB file size.

I assume, since your plugin makes a very solid impression, IF at all there are files that have not been backed up it will either show in the log at the end of creating the package or it will show up in some sort of red writing at the Step 3 summary, right?

You can be sure I am really really enjoying this plugin and as soon as I have got a few WP clients going and maintenance, uploading, downloading, deploying, etc. takes too much time your plugin will be the first one to be considered for going Pro.

Really amazing work! So easy and it just works and works and works! Thank you. ??

Important addition.

I assume the file size limit is done in binary notation?

define("DUPLICATOR_SCAN_WARNFILESIZE", 3145728); //3MB

3 MB = 3145728 Bytes (in binary)

Is the file size maximum limit set somewhere else in the plugin or could I technically set the file site limit also to

50 MB = 52428800 Bytes (in binary)

?

Thank you.

Kind Regards