Macrura

@ryan looks like this version number may be breaking version comparisons (?) edit: nevermind... only breaks with string comparisons, not with version_compare()

If you have any modules that check for ProcessWire version and don't use PHP version_compare, but instead use a string comparison, the comparison will fail. The modules that I know of that use this are in the Selectize group of inputfields and are being updated to a new version that fixes this. UPDATE 1: All of my modules that used the bad version comparison will be updated by tomorrow. UPDATE 2: All of the Selectize modules are now updated to work with PW 3.0.100 (fixed version comparison)

you are in a subfolder? you shouldn't have that /processwire-master/ part unless you are running in a subdir does your site load the same on www and non www? some hosts let you configure that settings at the hosting control panel, and then you can only use Let's Encrypt with the www subdomain, one example is Dreamhost.

I'm using this on all new sites now.. I think it's quite stable, and maybe could be added to modules directory? thanks!

who is the host? do u have force www?

Could be browser cache?

I recently worked a lot with the import export; it all worked really well, no problems, but i had to view the json file and do some cleanup since it was a complex export/import process; Also i didn't do any repeaters; If you are careful and know how it works, and observe what @Robin S said, it should work well...

i haven't worked on this ajax module for several months so it really is not ready, but i do have a working version if you want to try it. It needs testing, and work; The screenshots show some elements of the setup in case of any confusion. ---the field--- ---the files--- InputfieldSelectizeAjax.js InputfieldSelectizeAjax.module

@Ivan Gretsky i do have an inputfield version for ajax that is in development, i think it works pretty well; i can post back here once i am able to test it again - i will attach it to the post so you can try it out.

Been looking at the issue, as i have this being used on 3 sites; none of the sites are displaying events anymore, clients not too happy ()... The module itself though is doing it's job, so nothing wrong with the module; rather, the feeds are returning an empty array; we can only assume that this is something to do with Facebook new security, however even looking through the app settings and documentation, can't see how to debug this through facebook.. UPDATE: I saw this announcement here https://www.codeofaninja.com/2011/07/display-facebook-events-to-your-website.html Guess we're waiting for FB at this point...

so one of the first things i did was change the global to g_settings https://github.com/outflux3/ProcessGeneralSettings/blob/master/GeneralSettings.module#L31 besides that i added support for placeholders, collapsed states, markup, import/export of settings.. +1, i'm super paranoid about global vars now, since i lost all of the listers on one site... not sure if this problem still exists, i may have posted an issue report on the LP thread and Ryan may have changed it, haven't checked though...\ did you encounter any problems with LP? i usually use more verbose globals for that, but on the other hand i have a new module that uses a $meta global, and another one with $theme; sometimes it's nice for the globals to be concise

My module (Settings Factory) has no relation to this module (General Settings), it doesn't share or inherit any code. Settings Factory does not set a global var for the settings (that is left to the user and how they interact with the SF api), therefore it does not suffer from the same issue which is that this module by default/upon installation sets a global $wire var for $settings, which is already being used by LP. I don't personally endorse or promote, or recommend this module – i advise that it NOT be used until the $settings problem is fixed; as i stated in earlier posts, i used it on a couple of sites, forked it and fixed all the issues, but for the last 10 months i only use Settings Factory and i don't use this module at all. It is fine with me if this module is deprecated.

Objectively, this module provides a clever interface for adding fields to your settings. My fork of it supported more fields, and other improvements. The warning here, as is mentioned earlier in this thread is that you do not want to install this module if you use Lister Pro, there is a serious incompatibility that causes your Lister Pro listers to lose their settings. Besides that, Settings Factory allows multiple settings pages (unlimited) that you can link to in your admin menus; this module would be a single settings screen only. Further, you must use the fork if you want to have the settings be accessible to non-Superusers.

Looks cool, but I'm sort of addicted to the WireRender Pattern now... https://github.com/NinjasCL-processwire/wire-render-pattern https://medium.com/@clsource/the-wire-render-pattern-806bf6d6097a

@pmarkii can take it over if you want, and i do have an updated version as described above.

yes, if you need to hold those sorts of things, especially images, you should stick with real fields. The main advantages of using a settings module could be summed up as: (1) fast an easy to add a settings page (since you can reuse the same json file) and don't need to setup fields (2) dedicated edit screen with no tabs as on the edit screen (no children, settings etc), no delete (3) settings stored as JSON in 1 table/field (module config) (4) human readable editing url, no url param (5) since it is a process module, easy to link to the settings page directly in the admin menus more discussions on the Settings Factory topic..

i would stick with your regular fields page for editing settings; I don't think this module is maintained; i have a fork of it with a lot of new features and I use it on some sites, but then i made the Settings Factory module, so I use that instead now. You should be aware that the stock module is only accessible to super admin; one of my mods to the module was to create the permissions to enable other users to access settings; also i had to split it into a process module and the module that holds the settings, else settings not accessible to front end etc..

Hadn't predicted that need, but i can look into it...

>What version of Tracy are you running? 4.9.31 >When you say "but not any source" do you mean that lime 89 is blank? That's what I am seeing on the latest version. the error doesn't show any source file (template or module), just the error i posted. these are coming in through email; i'm not d() or bd(), at least as far as i know there none of those actively in any template or module files

Hi Adrian - quick question, i'm getting this warning every day, just wondering if it could be something in my code, or what i should look for, as it is referencing TD.php, but not any source, maybe a misconfiguration of the module.. PHP Warning: in_array() expects parameter 2 to be array, null given in ...site/assets/cache/FileCompiler/site/modules/TracyDebugger/includes/TD.php:89

@MarcoPLY, I've never tried the media={media} parameter; But in general the way this works is you have to have the correct markup on the page itself, meaning valid og tags and twitter card in the header. Maybe you already know this and are trying to override, but if not.... <meta property='og:image' content='bsolute/link/to/image.jpg' /> <meta property='og:image:url' content='absolute/link/to/image.jpg' /> <meta property='og:image:type' content='png' /> <meta property='og:image:width' content='1200' /> <meta property='og:image:height' content='630' /> <meta name='twitter:card' content='summary_large_image' /> <meta name='twitter:site' content='your-twitter-handle' /> <meta name='twitter:title' content='Page Title' /> <meta name='twitter:description' content='Some description' /> <meta name='twitter:creator' content='your-twitter-handle' /> <meta name='twitter:image:src' content='absolute/link/to/image.jpg' />

it's really pretty easy, just get a json array of the data and use DataTables to output the data.. the DataTables documentation is good enough to get you going, should you decide to try it out..

$date->getUnformatted("date") that method is only going o work for a field, like $page->getUnformatted("field")'

you can just pass the path of the page that handles the segments; if you are on the page, then $page is what you want. how can the system know which part of the URL is the segment? The whole point of URL segments is that they are not real pages, so there is no way to "look them up".

you can also just return $this->halt() at the end of your ajax template... (similar to exit as @kongondo posted but possibly a tad more elegant ( https://processwire.com/blog/posts/processwire-2.6.8-brings-new-version-of-reno-admin-theme-and-more/#new-this-gt-halt-method-for-use-in-template-files )